I think you have two choices.
1) Use another LDAP server for this purpose. Under linux I use OpenLdap
for my PKI and other needs.
2) Write a JNDI SPI for your database interface. This will allow you to
code to JNDI, but use the database as your store.
> Greetings.
> We have an application which requires storing user ids and passwords
> along with roles to do authorization and authentication. Since the
> implementation is on EJB, the natural way for solving this was to use
> ldap provided by the vender's EJB implementation. Due to the reasons
> beyond our control we cannot use ldap for this purpose. However there
> is a need to use java.security.Identity obtained from EJBContext in
> our Entity beans.
> Since we cannot use ldap we are planning to store user id, passwords
> and roles information in the backend database. Write some api's to do
> authorization and authentication. In this situation, I belive I will
> not be able to get the necessary information from the
> java.security.Identity.
>
> We are using NAS 4.0 SP2.
>
> Has anybody faced this kind of situation. How to solve this problem?
> Pointers, suggestions are highly appreciated.
>
> Thanks with regards,
> Ravindra
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
