KEYCLOAK-17491 Move the key settings to the new Keys tab

securing_apps/topics/oidc/java/client-authentication.adoc

@@ -28,7 +28,7 @@ This is based on the https://tools.ietf.org/html/rfc7523[RFC7523] specification.
 the particular backchannel request (for example, code-to-token request) in the `client_assertion` parameter.
 
 * {project_name} must have the public key or certificate of the client so that it can verify the signature on JWT. In {project_name} you need to configure client credentials for your client. First you need to choose `Signed JWT` as the method of authenticating your client in the tab `Credentials` in administration console.
-Then you can choose to either:
+Then you can choose to either in the tab `Keys`:
 ** Configure the JWKS URL where {project_name} can download the client's public keys. This can be a URL such as  \http://myhost.com/myapp/k_jwks (see details above). This option is the most flexible, since the client can rotate its keys anytime and {project_name} then always downloads new keys when needed without needing to change the configuration. More accurately,  {project_name} downloads new keys when it sees the token signed by an unknown `kid` (Key ID).
 ** Upload the client's public key or certificate, either in PEM format, in JWK format, or from the keystore. With this option, the public key is hardcoded and must be changed when the client generates a new key pair.
 You can even generate your own keystore from the {project_name} admininstration console if you don't have your own available.

server_admin/topics/clients/client-oidc.adoc

@@ -184,9 +184,8 @@ In Key Encryption, the client generates a key pair of asymmetric cryptography. T
 
 The client needs to pass their public key for encrypting CEK onto {project_name}. {project_name} supports downloading public keys from the URL the client provides. The client needs to provide their public keys according to https://tools.ietf.org/html/rfc7517[Json Web Keys (JWK)] specification. The way to do so is defined in `Signed JWT` of <<_client-credentials, Confidential Client Credentials>>. The detailed procedure is as follows:
 
-* open the client's `Credentials` tab
+* open the client's `Keys` tab
-* select `Signed Jwt` from `Client Authenticator` pulldown menu
+* toggle `JWKS URL` to ON
-* set ON to `JWKS URL` switch
 * input the client's public key providing URL on `JWKS URL` textbox
 
 Key Encryption's algorithms are defined in the https://tools.ietf.org/html/rfc7518#section-4.1[Json Web Algorithm (JWA)] specification. {project_name} supports RSAES-PKCS1-v1_5(RSA1_5), RSAES OAEP using default parameters (RSA-OAEP), and RSAES OAEP 256 using SHA-256 and MFG1 (RSA-OAEP-256). The detailed procedure to select this algorithm is as follows:

server_admin/topics/clients/client-saml.adoc

@@ -98,7 +98,7 @@ Encrypt Assertions::
 
 Client Signature Required::
   Expect that documents coming from a client are signed.
-  {project_name} will validate this signature using the client public key or cert set up in the `SAML Keys` tab.
+  {project_name} will validate this signature using the client public key or cert set up in the `Keys` tab.
 
 Force POST Binding::
   By default, {project_name} will respond using the initial SAML binding of the original request.

server_admin/topics/clients/oidc/confidential.adoc

@@ -20,9 +20,13 @@ Alternatively, you can opt to use a signed Json Web Token (JWT) or x509 certific
 .Signed JWT
 image:{project_images}/client-credentials-jwt.png[]
 
-When choosing this credential type you will have to also generate a private key and certificate for the client.  The private key
+When choosing this credential type you will have to also generate a private key and certificate for the client in the tab `Keys`.
-will be used to sign the JWT, while the certificate is used by the server to verify the signature.  Click on the
+The private key will be used to sign the JWT, while the certificate is used by the server to verify the signature.
-`Generate new keys and certificate` button to start this process.
+
+.Keys Tab
+image:{project_images}/client-oidc-keys.png[]
+
+Click on the `Generate new keys and certificate` button to start this process.
 
 .Generate Keys
 image:{project_images}/generate-client-keys.png[]