Nikhil, We are not sure at this time if the Turbine Security Scheme works for our scenario, we want to implement a centralized security repository, we talk about applications, groups, roles (within applications), permissions, and users. We are reviewing if we can use the Turbine Security Schema just like that, or if we have to modified, or extend some classes e.g AccessControlList, etc.
> The only solution I can think of is to have a table with two columns (username and id) and always sync with LDAP (either > in real-time, when the user logs in OR in batch). The mapping of username and id will remain stable since nothing will > change. We are considering the same approach, and the use of a scheduled job responsible for the sync between LDAP and RDBMS. Edgar -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
