Set up OIDC configuration within Azure by selecting the type as Web and with the redirect URI pointing to your deployment, as seen in the image below.
Redirect URL -
Once the registration is successful, create a new client secret and copy the secret value immediately after it is created without refreshing the page.
You will not be able to access the
client secretlater because it is shown ONCE and not repeated
The following details are required
- OpenID Connect metadata document
- Application (client) ID
- Newly created client secret
The following details can be obtained from the
OpenID Connect metadata document URI.
- Response Types Supported
- Response Modes Supported
- Scopes Supported
Step 1 Create a
<secret-filename>.yaml file with the following template.
All the values must be base64 encoded
In mac you can run
echo -n "string to be encoded" | base64to get the encoded value
Step 2 Update the k8s secret in the namespace of that cluster using the above file.
Step 3 Update the Helm variable
fiddler-sso-azuread-credentials value. If you are using the helm values file, use the following settings.
Once the deployments are updated, the new SSO settings will be applied.
Detailed instructions for deploying an SSO-enabled cluster - Creating Multi-org w/ SSO enabled cluster in Dev | SSO enabled cluster
Updated 28 days ago