-
Hello everyone, with the help of Answer of xfact-joseph-p on Issue 1434 I was able to setup oicd configuration, using oicd together with Authentik.
On the way back from Authentik to Semaphore using the redirect link an error gets thrown in the logs: time="2023-12-02T13:18:24Z" level=error msg="claim 'email' missing from id_token or not a string" This is the config of the "oidc_providers": {
"authentik": {
"display_name": "Sign in with SSO",
"provider_url": "https://auth.example.com/application/o/semaphore/",
"client_id": "<<Client_ID>>",
"client_secret": "<<Secret>>",
"redirect_url": "https://semaphore.example.com/api/auth/oidc/authentik/redirect",
"scopes": ["email", "openid", "profile"],
"username_claim": "preferred_username",
"name_claim": "preferred_username"
}
}, Authentik is providing the 'email', 'openid' and 'profile': The Has someone a clue what I am missing in the setup? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
Hello together, Well for what it's worth, I have a working setup now. Let me write down the working config, so it might help someone else: The
Authentik side: Redirect URIs/Origins (RegEx): Use the default settings for the Application Using this settings semaphore is able to create a user based on the scopes provided by Authentik. Let me know if someone else could get the OIDC setup working for them. Regards |
Beta Was this translation helpful? Give feedback.
Hello together,
Well for what it's worth, I have a working setup now.
Let me write down the working config, so it might help someone else:
The
oidc_providers
ofconfig.json
for Semaphore: