Hi, I think that's probably the easiest/most common solution. You have one authoritative source for usernames & passwords (LDAP or DB). CAS interfaces with that to service authentication requests. Your individual web applications use CAS for authentication.
As far as how you want to do the authorization, it's really up to you. It generally doesn't involve CAS. You could use one database for each app, you could have the 2 apps share the same database, or you could even connect back to the same LDAP or DB server that CAS is using for information other than what is required for username/password verification. -ScottH -----Original Message----- From: Pietro [mailto:[email protected]] Sent: Wednesday, July 06, 2011 4:22 PM To: [email protected] Subject: RE:[cas-user] CAS Best Practice with multiple web application Hi Scott, correct me if I get wrong, I should have a central user/pwd repository (database or Ldap) that contains users from WebApp_1 and WebApp_2 so I have to use it with CAS for Authentication Only. For Authorization or users Role I should use WebApp own database... Is it the right/best way? Thanks in advance. Pietro. -- 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
