How to handle user information with Spring Security, Spring LDAP, and Hibernate?

I use this for all Spring development. It has section on LDAP and integrating with bernate.

I use this for all Spring development. It has section on LDAP and integrating with manning. Com/walls4.

If you can not drop the user table at all, because it is used from other entities, then my suggestion is to separete the security stuff from the business stuff. This mean remove the only for security needed information from the user table (login, password, ...), so that only the stuff remains that is needed to implement the buiness cases. Then rewrite the security stuff so that is is based on the LDAP.

I guess you find a way to get the user data base object for an given prinipal. Only one thing will remain, how to create new user database entities if a new person get a new login. You have 3 choices, what is the best one strongly depends on your application: Create the database entity if the users first login Create the database entity if you first need it Create the database entity when it is created in the LDAO (or some minites later) for example with an cron job, or some Spring Scheduling service.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.