Crowd 2.1 : Specifying the Directory Order for an Application
This page last changed on Nov 30, 2010 by smaddox.
When you map multiple directories to an application, you also need to define the directory order. The directory order is important during the authentication of the user, in cases where the same user exists in multiple directories. When a user attempts to log in to an application, Crowd will search the directories in the order you specified, and will use the credentials (password) of the first occurrence of the user to validate the login attempt. See diagram below. The directory order is also important when granting the user access to an application based on group membership. In the case of multiple directories, Crowd looks at the group memberships based on the directory order. See below. On this page: Specifying the Directory OrderTo specify the directory order,
Screenshot: 'Application---Mapped Directories'
How Authentication WorksThe directory order is important during the authentication of the user. Let's assume that JIRA has been set up as a Crowd application, and has been mapped to two directories, 'Partners' and 'Customers', in that order. How Authorisation via Group Membership WorksThe directory order is important when granting the user access to an application based on group membership. When Crowd determines a person's access to an application based on their membership of a group, what happens if the same username exists in more than one directory? Crowd will look for group membership only in the first directory where the username appears, based on the order of directories mapped to the application. See Specifying the Directory Order for an Application. For example:
RELATED TOPICS
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
Document generated by Confluence on Nov 30, 2010 23:53 |