docs/content/integration/openid-connect/clients/semaphore/index.md
{{% oidc-common %}}
This example makes the following assumptions:
https://semaphore.{{< sitevar name="domain" nojs="example.com" >}}/https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/semaphoreinsecure_secretSome of the values presented in this guide can automatically be replaced with documentation variables.
{{< sitevar-preferences >}}
The following YAML configuration is an example Authelia client configuration for use with Semaphore which will operate with the application example:
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
- client_id: 'semaphore'
client_name: 'Semaphore'
client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng' # The digest of 'insecure_secret'.
public: false
authorization_policy: 'two_factor'
require_pkce: false
pkce_challenge_method: ''
redirect_uris:
- 'https://semaphore.{{< sitevar name="domain" nojs="example.com" >}}/api/auth/oidc/authelia/redirect'
scopes:
- 'openid'
- 'profile'
- 'email'
response_types:
- 'code'
grant_types:
- 'authorization_code'
access_token_signed_response_alg: 'none'
userinfo_signed_response_alg: 'none'
token_endpoint_auth_method: 'client_secret_basic'
To configure Semaphore there is one method, using the Configuration File.
{
"oidc_providers": {
"authelia": {
"display_name": "Authelia",
"provider_url": "https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}",
"client_id": "semaphore",
"client_secret": "insecure_secret",
"redirect_url": "https://semaphore.{{< sitevar name="domain" nojs="example.com" >}}/api/auth/oidc/authelia/redirect",
"scopes": ["openid", "profile", "email"],
"username_claim": "preferred_username",
"email_claim": "email",
"name_claim": "name",
"order": 1
}
}
}