From d152d0737890909f9fa934c1b593147be5120937 Mon Sep 17 00:00:00 2001 From: stianst Date: Mon, 7 Jun 2021 13:53:52 +0200 Subject: [PATCH] Fix missing image in RH-SSO docs --- .../policy/create-client-scope.png | Bin ...y-client-scope-policy-required-client-scope.adoc | 2 +- .../topics/policy-client-scope-policy.adoc | 2 +- .../client-oidc-keys.png | Bin server_admin/topics/clients/oidc/confidential.adoc | 2 +- 5 files changed, 3 insertions(+), 3 deletions(-) rename authorization_services/{keycloak-images => images}/policy/create-client-scope.png (100%) rename server_admin/{keycloak-images => images}/client-oidc-keys.png (100%) diff --git a/authorization_services/keycloak-images/policy/create-client-scope.png b/authorization_services/images/policy/create-client-scope.png similarity index 100% rename from authorization_services/keycloak-images/policy/create-client-scope.png rename to authorization_services/images/policy/create-client-scope.png diff --git a/authorization_services/topics/policy-client-scope-policy-required-client-scope.adoc b/authorization_services/topics/policy-client-scope-policy-required-client-scope.adoc index b72e4827d5..2df7d56910 100644 --- a/authorization_services/topics/policy-client-scope-policy-required-client-scope.adoc +++ b/authorization_services/topics/policy-client-scope-policy-required-client-scope.adoc @@ -4,7 +4,7 @@ When creating a client scope-based policy, you can specify a specific client scope as `Required`. When you do that, the policy will grant access only if the client requesting access has been granted *all* the *required* client scopes. .Example of Required Client Scope -image:{project_images}/policy/create-client-scope.png[alt="Example of Required Client Scope"] +image:images/policy/create-client-scope.png[alt="Example of Required Client Scope"] To specify a client scope as required, select the `Required` checkbox for the client scope you want to configure as required. diff --git a/authorization_services/topics/policy-client-scope-policy.adoc b/authorization_services/topics/policy-client-scope-policy.adoc index 6158bc4af6..2d3f4ca833 100644 --- a/authorization_services/topics/policy-client-scope-policy.adoc +++ b/authorization_services/topics/policy-client-scope-policy.adoc @@ -8,7 +8,7 @@ By default, client scopes added to this policy are not specified as required and To create a new client scope-based policy, select *Client Scope* in the dropdown list in the upper right corner of the policy listing. .Add Client Scope-Based Policy -image:{project_images}/policy/create-client-scope.png[alt="Add Client Scope-Based Policy"] +image:images/policy/create-client-scope.png[alt="Add Client Scope-Based Policy"] == Configuration diff --git a/server_admin/keycloak-images/client-oidc-keys.png b/server_admin/images/client-oidc-keys.png similarity index 100% rename from server_admin/keycloak-images/client-oidc-keys.png rename to server_admin/images/client-oidc-keys.png diff --git a/server_admin/topics/clients/oidc/confidential.adoc b/server_admin/topics/clients/oidc/confidential.adoc index 29a7a16ef4..cd3b6e8a98 100644 --- a/server_admin/topics/clients/oidc/confidential.adoc +++ b/server_admin/topics/clients/oidc/confidential.adoc @@ -24,7 +24,7 @@ When choosing this credential type you will have to also generate a private key The private key will be used to sign the JWT, while the certificate is used by the server to verify the signature. .Keys Tab -image:{project_images}/client-oidc-keys.png[] +image:images/client-oidc-keys.png[] Click on the `Generate new keys and certificate` button to start this process.