Hi Matt, Yes each application is currently mapped to the same database of users and roles: I'd like to know if there's a way to get username and password from the user a single time ( and authenticate him against the database or LDAP) and then let him navigate through the different applications, "propagating" the fact that he has authenticated to the other applications, without requiring him to input those informations again during his work session? Since each application will have a different HttpSession how can i share this information between apps? Should i pass username and password each time i switch application?
Thanks and sorry for my bad english! Andrea mraible wrote: > > You could modify the mappings for each application so their User and > Role objects read from the same database. Either that, or authenticate > against LDAP. If you decide to use LDAP, you'll want to remove the > User CRUD as it goes against the database and not LDAP. > > Matt > > On 2/22/08, rovi75 <[EMAIL PROTECTED]> wrote: >> >> Hi Matt, >> currently there is no sso for the applications in the product suite: >> every >> application still have its own login page. >> >> In the basic scenario I'll have to support at minimum a sso only between >> the >> apps in the .ear (sharing user roles and domain information from a local >> database). >> >> In a more complex scenario I'll probably have to support enterprise wide >> sso >> using directory services such as LDAP or even custom built legacy >> frameworks: in this case I would skip the login process completly and >> eventually even partially (e.g.starting the process by providing a login >> view that delegates authentication to a remote service ). >> >> >> Thanks >> >> >> >> mraible wrote: >> > >> > What SSO solution is already in place? Are you looking to share >> > usernames and passwords across applications, or completely skip the >> > login process across applications? >> > >> > Matt >> > >> > On 2/21/08, rovi75 <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi All, >> >> I'm trying to share the same authentication information between >> >> multiple >> >> appfuse (1.9.4) apps deployed inside a .ear in application server >> >> compliant >> >> win servlet specs 2.3. >> >> >> >> I see in many wiki that the preferred way to introduce sso in >> appfuse is >> >> integrating with CAS. The question is, since the product i'm >> developing >> >> will >> >> be deployed in environments with SSO already in place and others >> with no >> >> SSO >> >> at all, what's the best thing to do to accomplish a single sign on >> >> solution >> >> limited to the applications in the product suite? >> >> >> >> Thanks in advance, >> >> Andrea >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/single-sign-on-between-multiple-appfuse-based-apps-tp15607276s2369p15607276.html >> >> Sent from the AppFuse - User mailing list archive at Nabble.com. >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> >> -- >> View this message in context: >> http://www.nabble.com/single-sign-on-between-multiple-appfuse-based-apps-tp15607276s2369p15630044.html >> >> Sent from the AppFuse - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/single-sign-on-between-multiple-appfuse-based-apps-tp15607276s2369p15641532.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
