2019-07-15 23:31:08 -04:00
---
type: reference
2020-06-08 14:08:27 -04:00
stage: Manage
2022-01-26 22:14:06 -05:00
group: Authentication and Authorization
2022-09-21 17:13:33 -04:00
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
2019-07-15 23:31:08 -04:00
---
2022-08-11 02:12:18 -04:00
# Atlassian Crowd OmniAuth provider (deprecated) **(FREE SELF)**
WARNING:
This feature was [deprecated ](https://gitlab.com/gitlab-org/gitlab/-/issues/369117 ) in GitLab 15.3 and is planned for
removal in 16.0.
2017-03-07 12:58:30 -05:00
2020-12-08 07:09:53 -05:00
Authenticate to GitLab using the Atlassian Crowd OmniAuth provider. Enabling
this provider also allows Crowd authentication for Git-over-https requests.
2019-07-15 23:31:08 -04:00
2017-03-07 12:58:30 -05:00
## Configure a new Crowd application
1. Choose 'Applications' in the top menu, then 'Add application'.
1. Go through the 'Add application' steps, entering the appropriate details.
The screenshot below shows an example configuration.
2019-07-11 22:06:46 -04:00
![Example Crowd application configuration ](img/crowd_application.png )
2017-03-07 12:58:30 -05:00
## Configure GitLab
1. On your GitLab server, open the configuration file.
2019-07-11 22:06:46 -04:00
**Omnibus:**
2017-03-07 12:58:30 -05:00
2020-01-30 10:09:15 -05:00
```shell
2019-07-11 22:06:46 -04:00
sudo editor /etc/gitlab/gitlab.rb
```
2017-03-07 12:58:30 -05:00
2019-07-11 22:06:46 -04:00
**Source:**
2017-03-07 12:58:30 -05:00
2020-01-30 10:09:15 -05:00
```shell
2019-07-11 22:06:46 -04:00
cd /home/git/gitlab
2017-03-07 12:58:30 -05:00
2019-07-11 22:06:46 -04:00
sudo -u git -H editor config/gitlab.yml
```
2017-03-07 12:58:30 -05:00
2021-11-09 13:13:13 -05:00
1. See [Configure initial settings ](../../integration/omniauth.md#configure-initial-settings )
2017-03-07 12:58:30 -05:00
for initial settings.
1. Add the provider configuration:
2019-07-11 22:06:46 -04:00
**Omnibus:**
```ruby
gitlab_rails['omniauth_providers'] = [
{
2021-11-19 04:13:48 -05:00
name: "crowd",
# label: "Provider name", # optional label for login button, defaults to "Crowd"
args: {
crowd_server_url: "CROWD_SERVER_URL",
application_name: "YOUR_APP_NAME",
application_password: "YOUR_APP_PASSWORD"
2019-07-11 22:06:46 -04:00
}
}
]
```
**Source:**
2020-03-05 22:08:08 -05:00
```yaml
2019-07-11 22:06:46 -04:00
- { name: 'crowd',
2021-11-19 04:13:48 -05:00
# label: 'Provider name', # optional label for login button, defaults to "Crowd"
2019-07-11 22:06:46 -04:00
args: {
crowd_server_url: 'CROWD_SERVER_URL',
application_name: 'YOUR_APP_NAME',
application_password: 'YOUR_APP_PASSWORD' } }
```
2022-08-02 20:10:17 -04:00
1. Change `CROWD_SERVER_URL` to the [base URL of your Crowd server ](https://confluence.atlassian.com/crowdkb/how-to-change-the-crowd-base-url-245827278.html ).
2017-03-07 12:58:30 -05:00
1. Change `YOUR_APP_NAME` to the application name from Crowd applications page.
1. Change `YOUR_APP_PASSWORD` to the application password you've set.
1. Save the configuration file.
2022-08-02 20:10:17 -04:00
1. [Reconfigure ](../restart_gitlab.md#omnibus-gitlab-reconfigure ) (Omnibus GitLab) or [restart ](../restart_gitlab.md#installations-from-source ) (source installations) for
the changes to take effect.
2017-03-07 12:58:30 -05:00
On the sign in page there should now be a Crowd tab in the sign in form.
2018-01-10 13:18:39 -05:00
## Troubleshooting
2022-08-02 20:10:17 -04:00
### Error: "could not authorize you from Crowd because invalid credentials"
2018-01-10 13:18:39 -05:00
2022-08-02 20:10:17 -04:00
This error sometimes occurs when a user attempts to authenticate with Crowd. The
Crowd administrator should consult the Crowd log file to know the exact cause of
this error message.
2018-01-10 13:18:39 -05:00
2022-08-02 20:10:17 -04:00
Ensure the Crowd users who must sign in to GitLab are authorized to the
2021-11-09 16:10:00 -05:00
[application ](#configure-a-new-crowd-application ) in the **Authorization** step.
2020-11-09 19:08:52 -05:00
This could be verified by trying "Authentication test" for Crowd (as of 2.11).
2018-01-10 13:18:39 -05:00
2021-11-09 16:10:00 -05:00
![Example Crowd application authorization configuration ](img/crowd_application_authorisation.png )