Well.. important is only that CAS is able to authenticate the user and report this to the cas client on the other side. if that user has a different password there actually doesnt matter since you could modify the login process to ignore it when cas reports a user to be authenticated. in exotic scenarios you might even be able to create some code for getting users in a specific format
But yea, basically it makes things much easier if the user/pw are the same everywhere On 10/7/2010 4:23 AM, Scott Battaglia wrote: > I'm not sure I follow. CAS is a single sign on server. Thus its for > the most part, essential, that you've solved your identity problem (or > at least can have CAS abstract it). If you require each site to have > its own password, then single sign on isn't going to work very well. > If you've got namespace collision for usernames, then CAS isn't going > to work correctly. > > > On Wed, Oct 6, 2010 at 9:05 AM, SubbaRao <[email protected] > <mailto:[email protected]>> wrote: > > Did you mean we need to maintain same passwords even the platforms > are different. > -- > You are currently subscribed to [email protected] > <mailto:[email protected]> as: [email protected] > <mailto:[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 -- 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
