Basics - SecurityPage commented by Trenton D. AdamsIs it true that credentials are only propagated on the very first call to the back end, of a stateful session bean? i.e. subsequent calls are trusted for that session, and the credential is ditched, but the principal keeps propagating? Is it true the credentials are cached and propagated on every call of a stateless bean? If not, are they are passed on the first one, and some other method is used after authentication is established (such as a token)? Can I force authentication to go through the back end EJB server, propagate the trust forward, and not be done by the front end tomcat/openejb?
Change Notification Preferences
View Online
|
|
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
- [CONF] OpenEJB 3.0.x documentation > Basics - Security confluence
