debian-mirror-gitlab/doc/administration/auth/crowd.md

88 lines
2.8 KiB
Markdown
Raw Normal View History

2019-09-30 21:07:59 +05:30
---
type: reference
2020-06-23 00:09:42 +05:30
stage: Manage
group: Access
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
2019-09-30 21:07:59 +05:30
---
2017-08-17 22:00:37 +05:30
# Atlassian Crowd OmniAuth Provider
2019-09-30 21:07:59 +05:30
Authenticate to GitLab using the Atlassian Crowd OmniAuth provider.
2017-08-17 22:00:37 +05:30
## 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-09-30 21:07:59 +05:30
![Example Crowd application configuration](img/crowd_application.png)
2017-08-17 22:00:37 +05:30
## Configure GitLab
1. On your GitLab server, open the configuration file.
2019-09-30 21:07:59 +05:30
**Omnibus:**
2017-08-17 22:00:37 +05:30
2020-03-13 15:44:24 +05:30
```shell
2019-09-30 21:07:59 +05:30
sudo editor /etc/gitlab/gitlab.rb
```
2017-08-17 22:00:37 +05:30
2019-09-30 21:07:59 +05:30
**Source:**
2017-08-17 22:00:37 +05:30
2020-03-13 15:44:24 +05:30
```shell
2019-09-30 21:07:59 +05:30
cd /home/git/gitlab
2017-08-17 22:00:37 +05:30
2019-09-30 21:07:59 +05:30
sudo -u git -H editor config/gitlab.yml
```
2017-08-17 22:00:37 +05:30
1. See [Initial OmniAuth Configuration](../../integration/omniauth.md#initial-omniauth-configuration)
for initial settings.
1. Add the provider configuration:
2019-09-30 21:07:59 +05:30
**Omnibus:**
```ruby
gitlab_rails['omniauth_providers'] = [
{
"name" => "crowd",
"args" => {
"crowd_server_url" => "CROWD_SERVER_URL",
"application_name" => "YOUR_APP_NAME",
"application_password" => "YOUR_APP_PASSWORD"
}
}
]
```
**Source:**
2020-04-08 14:13:33 +05:30
```yaml
2019-09-30 21:07:59 +05:30
- { name: 'crowd',
args: {
crowd_server_url: 'CROWD_SERVER_URL',
application_name: 'YOUR_APP_NAME',
application_password: 'YOUR_APP_PASSWORD' } }
```
2017-08-17 22:00:37 +05:30
1. Change `CROWD_SERVER_URL` to the URL of your Crowd server.
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.
2020-05-24 23:13:21 +05:30
1. [Reconfigure](../restart_gitlab.md#omnibus-gitlab-reconfigure) or [restart](../restart_gitlab.md#installations-from-source) for the changes to take effect if you
2017-08-17 22:00:37 +05:30
installed GitLab via Omnibus or from source respectively.
On the sign in page there should now be a Crowd tab in the sign in form.
2018-03-17 18:26:18 +05:30
## Troubleshooting
If you see an error message like the one below when you sign in after Crowd authentication is configured, you may want to consult the Crowd administrator for the Crowd log file to know the exact cause:
2020-03-13 15:44:24 +05:30
```plaintext
2018-03-17 18:26:18 +05:30
could not authorize you from Crowd because invalid credentials
```
Please make sure the Crowd users who need to login to GitLab are authorized to [the application](#configure-a-new-crowd-application) in the step of **Authorisation**. This could be verified by try "Authentication test" for Crowd as of 2.11.
2019-09-30 21:07:59 +05:30
![Example Crowd application authorisation configuration](img/crowd_application_authorisation.png)