Alexandre_Saudate 2 de fev. de 2010
Qual gerenciador de SSO você está usando? Trabalhei com o Oracle SSO e ele suportava muito bem aplicações externas…
[]´s
dipeloco 2 de fev. de 2010
Segue documento abaixo ..... porem qualquer duvida pode perguntar ..... e utilize JAAS.
Se precisar pesquisar mais coisas na net e vai precisar.... utilize o termo Single Sign On
Single Sign On
In many environments , but particularly in portal environments , it is desireable to have a user challenged to authenticate themselves only once over a set of web applications deployed on a particular virtual host . This can be accomplished by nesting an element like this inside the Host element for this virtual host :
& lt ; Host name = "localhost" ...& gt ;
...
& lt ; Valve className = "org.apache.catalina.authenticator.SingleSignOn" /& gt ;
...
& lt ;/ Host & gt ;
The Single Sign On facility operates according to the following rules :
All web applications configured for this virtual host must share the same Realm . In practice , that means you can nest the Realm element inside this Host element ( or the surrounding Engine element ), but not inside a Context element for one of the involved web applications .
As long as the user accesses only unprotected resources in any of the web applications on this virtual host , they will not be challenged to authenticate themselves .
As soon as the user accesses a protected resource in any web application associated with this virtual host , the user will be challenged to authenticate himself or herself , using the login method defined for the web application currently being accessed .
Once authenticated , the roles associated with this user will be utilized for access control decisions across all of the associated web applications , without challenging the user to authenticate themselves to each application individually .
As soon as the user logs out of one web application ( for example , by invalidating the corresponding session if form based login is used ), the user ' s sessions in all web applications will be invalidated . Any subsequent attempt to access a protected resource in any application will require the user to authenticate himself or herself again .
The Single Sign On feature utilizes HTTP cookies to transmit a token that associates each request with the saved user identity , so it can only be utilized in client environments that support cookies .
