You can specify which principals (i.e. users) are allowed to authenticate against each application. For each mapped directory, you can either allow all users within the directory to authenticate with the application, or just particular groups within the directory. You can assign group membership to each principal.
For example, the default group crowd-administrators, which is automatically created in the default directory that you specified during setup, is allowed to access the Crowd Administration Console. This means that principals who belong to the group crowd-administrators are allowed to login to the Crowd Administration Console (assuming they supply a valid password).
To allow a group to access an application,
- Log in to the Crowd Administration Console.
- Click the 'Applications' link in the top navigation bar.
- This will display the Application Browser. Click the 'View' link that corresponds to the application you wish to map.
- This will display the 'View Application' screen. Click the 'Groups' tab.
- This will display a list of groups that currently have access to the application. Click the drop-down arrow next to the 'Add' button.
- This will display a selection-list of all the groups that exist within each directory. Select the new group from the drop-down list and click the 'Add' button.
Alternatively, you can allow all users from a particular directory to authenticate against the application. See 3.3 Mapping a Directory to an Application. |
Screenshot: 'Application---Specify Groups'
See Also
4. Managing Principals, Groups and Roles
Related Topics
- 3.1 Using the Application Browser
- 3.2 Adding an Application
- 3.2.01 Integrating Crowd with Apache
- 3.2.02 Integrating Crowd with Subversion
- 3.2.03 Integrating Crowd with Atlassian Confluence
- 3.2.04 Integrating Crowd with Atlassian CrowdID
- 3.2.05 Integrating Crowd with Atlassian FishEye
- 3.2.06 Integrating Crowd with Atlassian JIRA
- 3.2.07 Integrating Crowd with Jive Forums
- 3.2.08 Integrating Crowd with Atlassian Bamboo
- 3.2.09 Integrating Crowd with Acegi Security
- 3.2.10 Integrating Crowd with Atlassian Crucible
- 3.2.11 Integrating Crowd with a Custom Application
- 3.3 Mapping a Directory to an Application
- 3.4 Specifying which Groups can access an Application
- 3.5 Specifying an Application's Address or Hostname
- 3.6 Testing a User's Login to an Application
- 3.7 Managing an Application's Session
- 3.8 Deleting or Deactivating an Application






