Using the LDAP subscription provider to authenticate and register users in our web application Active Directory To allow users to provide usernames in other applications, we have to add a prefix to our user name and it should be as transparent and painless as possible.
One way to expand what I want is to be able to add a prefix to the user name before attaching or registering the LDAP membership provider membership. For example, if the user is in the input "1 AM> JOSE " 1 ... I want to certify: " App1_JohnS ".
How can I extend membership to fulfill it? What is being started right before certifying and registering any idea (to make users)?
Update: Every web app contains an "ou" in the ad from which to create and authenticate users but because it is just an active directory controller, the user name must be unique. We have to solve this issue using the membership provider and not add more ads.
When you create your search query string, why do not you prefix for DN (or UID) Do you add what you are looking for?
If you are stuck with an application that you can not modify, then I suggest that the use of the AD Group is the functionality - you are certified against the ED using a single user account. We do. After this, you can get all the properties for it, if the user has a group set, then grant access to the appropriate application.
Modifying which group a user is in is a trivial matter for your ad administrator, or you can do this if you have write access to the directory.
Comments
Post a Comment