this points out a very frustrating issue with blackboard's default CAS implementation: you either 1) get SSO but are forced to do cas logout, or 2) you aren't forced to do cas logout but the user has to type their password when they use CAS to access blackboard.
- Rex Roof WCC Systems Engineer <[email protected]> 734-973-3478 On Tue, Mar 18, 2014 at 7:57 PM, Paul B. Henson <[email protected]>wrote: > > From: Richard Frovarp > > Sent: Tuesday, March 18, 2014 2:41 PM > > > > That's not necessarily disagreeing with me. That's describing true SSO, > > because user's aren't prompted. > [...] > > theirs, as it makes the most sense to me. If you use the same > > credentials to login to two completely different places (and the same > > credentials are by design), I call that same sign on. I steadfastly > > refuse to use the SSO acronym or single sign on term for any system that > > asks for credentials again. > > It seems we had a communications breakdown, as I said: > > "There are really two ways to look at "SSO". The first is that you simply > use the > same username/password pair for every single service, even if you have to > authenticate separately to them. The second is that you authenticate once, > and > then can access every service without authenticating again." > > You then said: > > "There is SINGLE sign on (SSO) and SAME sign on. The second is same sign > on." > > However, in my description, the "second" was the one where you > authenticate once, and then not again. > > So it sounds like we agree on SSO, but simply failed to successfully > negotiate the description ;). > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
