2
Support for sending "resource" parameter during authentication for ADFS OIDC integration
Source: outline/outline#6362 · opened by @PrimaryMagic
Hi,
I've been encountering some issues while trying to connect outline with our on premise ADFS instance. Microsoft requires a custom "resource" parameter to be send for authentication as can be seen here ( or else it will fail with the following errors:
"Failed to parse response from Expected JSON, got: "
and
Bearer error="invalid_token", error_description="MSIS9921: Received invalid UserInfo request. Audience 'microsoft:identityserver:[client_identifier]' in the access token is not same as the identifier of the UserInfo relying party trust 'urn:microsoft:userinfo'."
I believe this is the same issue as [#4491]( but as far as i know, there hasn't been any solution to this yet. I'd like to know if there is any support planned to add a custom resource path in the .env OIDC-config to support OIDC authentication for ADFS.
I've been encountering some issues while trying to connect outline with our on premise ADFS instance. Microsoft requires a custom "resource" parameter to be send for authentication as can be seen here ( or else it will fail with the following errors:
"Failed to parse response from Expected JSON, got: "
and
Bearer error="invalid_token", error_description="MSIS9921: Received invalid UserInfo request. Audience 'microsoft:identityserver:[client_identifier]' in the access token is not same as the identifier of the UserInfo relying party trust 'urn:microsoft:userinfo'."
I believe this is the same issue as [#4491]( but as far as i know, there hasn't been any solution to this yet. I'd like to know if there is any support planned to add a custom resource path in the .env OIDC-config to support OIDC authentication for ADFS.
No pledges yet. Be the first to back this.
Comments
Similar requests
OIDC plugin ignores the standard "locale" claim when provisioning new accounts
1 vote · 0 comments
Config Option to forward login to /auth/oidc instead of the normal login screen.
3 votes · 0 comments
Restrict account creation based on OIDC `groups` claim
4 votes · 0 comments
Support for OIDC id_token_hint in Logout URL
4 votes · 0 comments
Use groups from OpenID Connect SSO provider
39 votes · 0 comments
No comments yet.