About Applications
Crowd integrates and provisions applications. Once defined, an application is mapped to a directory(s), whose users are then granted access to the application. Note that an application can only communicate with Crowd when the application uses a known host address.Default Applications
When you first use the Application Browser, you will see three default applications:
- 'crowd' — this is the Crowd Administration Console (i.e. the Crowd Administration Console is itself a web-application that is provisioned by Crowd). The 'crowd' application is mapped to the default directory which you defined during setup, and can be accessed by members of the
crowd-administratorsgroup. - 'demo' — this is the 'demo' application which you (optionally) configured during setup. Its main purpose is to provide an example of how to integrate custom applications with Crowd. To access the 'demo' application, go to http://localhost:8095/demo.
- 'crowdid' — this is the 'CrowdID application which you (optionally) configured during setup. It allows you to provide OpenID services to your end-users. For details please see the CrowdID 1.2 Administration Guide and the CrowdID 1.2 User Guide. To access CrowdID, go to http://localhost:8095/openidserver.
About the Application Browser
The Application Browser allows you to view and search for integrated applications.
To use the Application Browser,
- Login to the Crowd Administration Console.
- Click the 'Applications' link in the top navigation bar.
- This will display the Application Browser, showing all the applications that exist in your Crowd system. You can refine your search by specifying a 'Name' (note that this is case-sensitive), or 'Active'/'Inactive' applications.
- To view/edit an application's details, click the 'View' link.
Screenshot 1: 'Application Browser'

Screenshot 2: 'View Application'

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
Labels:






