I agree about preboarding.

SSO doesn't, I think, always require an additional login. We've been asked to authenticate the user against their AD login and the security path (well, the adspath), which we have done. We keep the username and adspath in our data, and verify against them. That's was I think of as SSO.

Hank

>You could be thinking about single sign-on, where the same UID/PWD combination is used on many different applications/ systems.
>
>However, IMO, this term is as inaccurate as "preboarding" that used by airlines. If it's single signon, I should only have to signon once, not multiple times (each app requires you to signon)
>
>Note re: Preboarding. Preboarding implies things that happen before boarding begins, but with airlines, preboarding is when people start boarding.
>
>>I agree with you as far as uniqueness and so on. I have an app that for many (20+) years has been set to use only a password. So the password is unique for each user. The user name is non-essential. I want to change this so I have to explain to the customers. I thought I heard the term 'Single-something' and 'Double-something'; so I would explain that we are changing from 'Single..' to 'Double...' But apparently I am mistaken and such terms do not exist. So I will simply have to describe.
>>Thank you.