Documentation for Federated (OIDC) Keystone adoption#1397
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Jira: https://redhat.atlassian.net/browse/OSPRH-19963 Signed-off-by: Andre Aranha <afariasa@redhat.com> Co-authored-by: Grzegorz Grasza <xek@redhat.com>
| [id="configuring-federation-for-keystone_{context}"] | ||
|
|
||
| = Configuring OIDC federation for the Identity service | ||
|
|
There was a problem hiding this comment.
| [role="_abstract"] |
This attribute is critical for when the docs team migrates to AEM.
|
|
||
| .Prerequisites | ||
|
|
||
| * You have Keycloak reachable from your {rhos_long} cluster. |
There was a problem hiding this comment.
| * You have Keycloak reachable from your {rhos_long} cluster. | |
| * Keycloak is reachable from your {rhos_long} cluster. |
| + | ||
| where: | ||
|
|
||
| `<keycloak-ca.crt>`:: Replace with the path to the CA file you want to use. |
There was a problem hiding this comment.
| `<keycloak-ca.crt>`:: Replace with the path to the CA file you want to use. | |
| `<keycloak-ca.crt>`:: Specifies the path to the CA file that you want to use. |
| + | ||
| where: | ||
|
|
||
| `<client_secret>`:: Replace with your client ID to use for the OIDC provider handshake. You must get this from your SSO administrator. |
There was a problem hiding this comment.
| `<client_secret>`:: Replace with your client ID to use for the OIDC provider handshake. You must get this from your SSO administrator. | |
| `<client_secret>`:: Specifies the client ID to use for the OIDC provider handshake. You must get the client ID from your SSO administrator. |
| where: | ||
|
|
||
| `<client_secret>`:: Replace with your client ID to use for the OIDC provider handshake. You must get this from your SSO administrator. | ||
| `<crypto_passphrase>`:: Replace with the client secret to use for the OIDC provider handshake. You must get this from your SSO administrator after providing your redirect URLs. |
There was a problem hiding this comment.
| `<crypto_passphrase>`:: Replace with the client secret to use for the OIDC provider handshake. You must get this from your SSO administrator after providing your redirect URLs. | |
| `<crypto_passphrase>`:: Specifies the client secret to use for the OIDC provider handshake. You must get the client secret from your SSO administrator after providing your redirect URLs. |
|
|
||
| `<client_secret>`:: Replace with your client ID to use for the OIDC provider handshake. You must get this from your SSO administrator. | ||
| `<crypto_passphrase>`:: Replace with the client secret to use for the OIDC provider handshake. You must get this from your SSO administrator after providing your redirect URLs. | ||
| `<LocationMatch>` and `<Location>`:: Replace with the chosen string that creates your unique redirect URL. |
There was a problem hiding this comment.
| `<LocationMatch>` and `<Location>`:: Replace with the chosen string that creates your unique redirect URL. | |
| `<LocationMatch>` and `<Location>`:: Specifies the chosen string that creates your unique redirect URL. |
| `<crypto_passphrase>`:: Replace with the client secret to use for the OIDC provider handshake. You must get this from your SSO administrator after providing your redirect URLs. | ||
| `<LocationMatch>` and `<Location>`:: Replace with the chosen string that creates your unique redirect URL. | ||
|
|
||
| . Patch the `OpenStackControlPlane` custom resource (CR) to enable OIDC federation for Keystone: |
There was a problem hiding this comment.
| . Patch the `OpenStackControlPlane` custom resource (CR) to enable OIDC federation for Keystone: | |
| . Patch the `OpenStackControlPlane` custom resource (CR) to enable OIDC federation for Keystone. Ensure that you merge the patch with any existing custom configuration for the {identity_service}: |
I think this information would be good for the customer to know upfront.
| + | ||
| * Ensure you merge the patch with any existing custom configuration for the {identity_service}. |
There was a problem hiding this comment.
| + | |
| * Ensure you merge the patch with any existing custom configuration for the {identity_service}. |
I moved the text above the code block.
Documentation for Federated (OIDC) Keystone adoption
Original Patch: #1062
Jira: https://issues.redhat.com/browse/OSPRH-19960
Jira: https://redhat.atlassian.net/browse/OSPRH-19963