Version Affected: All
Overview
This article addresses whether a SecureAuth CIAM Workspace used only for server-to-server OAuth flows can be fully restricted to OAuth, hiding OpenID Connect (OIDC) from its well-known endpoint.
Cause
A Workspace used only for server-to-server OAuth flows still exposes its full well-known endpoint, including OIDC-related sections the Workspace does not actually use.
Resolution:
It is not currently possible to disable entire sections of the well-known endpoint. The closest option is to disable the specific flows, scopes, and response types that the Workspace does not need.
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Comments
Please sign in to leave a comment.