blob: 4347ff84518e4189f0336371aa5996310369dcad (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
---
title: "Jira"
description: "Trusted Header SSO Integration for Jira"
lead: ""
date: 2022-05-16T21:15:52+10:00
draft: false
images: []
menu:
integration:
parent: "trusted-header-sso"
weight: 420
toc: true
community: true
aliases:
- /docs/community/using-remote-user-header-for-sso-with-jira.html
---
## Introduction
This is a guide on integration of __Authelia__ and [Jira] via the trusted header SSO authentication.
As with all guides in this section it's important you read the [introduction](../introduction.md) first.
## Tested Versions
* Authelia: v4.35.5
* Jira: Unknown
* EasySSO: Unknown
## Before You Begin
This example makes the following assumptions:
* The user accounts with the same names already exist in [Jira].
* You have purchased the third-party plugin from the [Atlassian marketplace](https://marketplace.atlassian.com/apps/1212581/easy-sso-jira-kerberos-ntlm-saml?hosting=server&tab=overview)
## Configuration
To configure [Jira] to trust the `Remote-User` and `Remote-Email` header do the following:
1. Visit the Easy SSO plugin settings
2. Under HTTP configure the `Remote-User` header
3. Check the `Username` checkbox
## See Also
* [EasySSO Documentation](https://techtime.co.nz/display/TECHTIME/EasySSO#documentation-area)
[Jira]: https://www.atlassian.com/software/jira
|
