# discourse-crowd

**Repository Path**: mirrors_discourse/discourse-crowd

## Basic Information

- **Project Name**: discourse-crowd
- **Description**: A plugin to enable authentication support for Atlassian Crowd
- **Primary Language**: Unknown
- **License**: MIT
- **Default Branch**: main
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2020-09-24
- **Last Updated**: 2026-05-23

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# ⚠️ This plugin is no longer supported

### discourse-crowd

A Discourse Plugin to enable authentication via Atlassian Crowd.


### Configuration For Docker Installations Of Crowd

Add the following to the 'env' section of your container/<app>.yml


`  #Support For Crowd Plugin`  
`  #Mode should be either 'separated' or 'mixed'`  
`  DISCOURSE_CROWD_SERVER_URL: <SERVER URL>`  
`  DISCOURSE_CROWD_APPLICATION_NAME: <USER_NAME>`  
`  DISCOURSE_CROWD_APPLICATION_PASSWORD: <PASSWORD>`  
`  DISCOURSE_CROWD_APPLICATION_MODE: <MODE>`  



### Configuration For Non Docker Installations

Add the following settings to your `discourse.conf` file:

- `crowd_server_url`
- `crowd_application_name`
- `crowd_application_password`
- `crowd_application_mode` - can be one of `separated` or `mixed`
- `crowd_validate_email` - uncheck this if your Crowd accounts do NOT validate email addresses.  This will force discourse to validate the email.

  
### Configuring Atlassian Group mappings

This part of the configuration allows users who login through discourse-crowd to automatically be added or removed from Discourse groups (at login time).
These can be configured by searching for `plugin:discourse-crowd` in Settings.
- `crowd_groups_enabled` turns crowd mapping on or off
- `crowd_groups_mapping` is a list of colon-separated pairs. The first of each pair is an Atlassian group and the second is a comma-separated list of discourse group "slugs" (the group name in the URL). e.g. `jira-users:git_group,user_group`
- `crowd_groups_remove_unmapped_groups` when enabled means a user will be _removed_ from the discourse group(s) that are mapped to if the user is _not_ in the corresponding Atlassian group.  You probably want this on, but because it might be wrongly removing users it's off by default.
  
### License

MIT