Integrating Crowd with a Custom Application

Crowd ships with out-of-the-box support for a number of applications. You can also integrate Crowd with other applications as follows:

Step 1. Configuring Crowd to talk to your Application

Please see Adding an Application.

Step 2. Configuring your Application to talk to Crowd

2.1 Developing a Crowd Client

For assistance, please see the developer's guide to creating a Crowd client for your custom application.

2.2 Configuring your Application

The integration libraries and configuration files are included in the Crowd download, in the client folder. You will find the Crowd integration library, and the client libraries on which the framework depends, in the lib folder. An example client properties file crowd.properties is located in the conf folder.

To configure your application, perform the following:

1. Copy the Crowd client and supporting libraries to your application's classpath, typically WEB-INF/lib.
   These files will be in Crowd's client folder, with a name similar to crowd-integration-client-X.X.X.jar and all supporting JARs in the client/lib folder.
2. Copy the client properties file crowd.properties to your application's deployment directory, typically WEB-INF/classes.
3. Edit the crowd.properties file to reflect the values of your deployment parameters. Refer to the description of the attributes in the crowd.properties file.

-Dcrowd.properties={FILE-PATH}/crowd.properties

RELATED TOPICS

• Using the Application Browser
• Adding an Application
  • Integrating Crowd with Atlassian Bamboo
  • Integrating Crowd with Atlassian Confluence
    • Integrating Crowd with Atlassian Confluence 3.4 or earlier
    • Updating Files in a Confluence Evaluation Distribution
  • Integrating Crowd with Atlassian CrowdID
  • Integrating Crowd with Atlassian Crucible
  • Integrating Crowd with Atlassian FishEye
    • Configuring FishEye earlier than 4.0 with Crowd
  • Integrating Crowd with Atlassian JIRA
    • Integrating Crowd with Atlassian JIRA 4.2 or earlier
  • Integrating Crowd with Atlassian Bitbucket Server
  • Integrating Crowd with Acegi Security
    • Integrating AppFuse - a Crowd-Acegi Integration Tutorial
  • Integrating Crowd with Apache
    • Disabling Previous Versions of the Crowd Apache Connector
    • Installing the Crowd Apache Connector on CentOS Linux
    • Installing the Crowd Apache Connector on Red Hat Enterprise Linux
    • Installing the Crowd Apache Connector on Ubuntu Linux
    • Installing the Crowd Apache Connector on Debian
    • Installing the Crowd Apache Connector on Other UNIX-Like Systems
    • Installing the Crowd Apache Connector on Windows
  • Integrating Crowd with Jive Forums
    • Jive SSO
  • Integrating Crowd with Spring Security
    • Integrating AppFuse - a Crowd-Spring Security Integration Tutorial
  • Integrating Crowd with Subversion
  • Integrating Crowd with a Custom Application
  • Integrating Crowd with Atlassian HipChat
• Configuring the Google Apps Connector
• Mapping a Directory to an Application
  • Specifying the Directory Order for an Application
  • Specifying an Application's Directory Permissions
    • Example of Directory Permissions
  • Viewing Users in Directories Mapped to an Application
  • Specifying which Groups can access an Application
• Effective memberships with multiple directories
• Specifying an Application's Address or Hostname
• Testing a User's Login to an Application
• Enforcing Lower-Case Usernames and Groups for an Application
• Managing an Application's Session
• Deleting or Deactivating an Application
• Configuring Caching for an Application
• Overview of SSO
• Configuring Options for an Application

Crowd 3.0 beta documentation