|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
EJB, custom Realm and LoginModule, cache authentication result
Submitted by Narcom on Mon, 08/17/2009 - 03:30.
Tags:
I created custom Realm and LoginModule for Glassfish application server. I took as example this URL http://developers.sun.com/appserver/reference/techart/as8_authentication...
As I see on every lookup and method invocation from application client it sends my login and password to server. I want to say that EJB authentication behavior is not like with “http session”.
Every request cause my authenticateUser() method invocation. I cannot afford to check login credentials on every such request. As result I think I need store login result and all user data in some temporarily storage. I can store it in memory and start another process to delete expired “Sessions” but I want store it on disk.
And my question is – is there some ready implementation for this task? Or how do I cache authentication results using cluster aware methods?