Each adapter supported by Keycloak can be configured by a simple JSON text file. This is what one might look like: Some of these configuration switches may be adapter specific and some are common across all adapters. For Java adapters you can use ${...} enclosure as System property replacement. For example ${jboss.server.config.dir}. Also, you can obtain a template for this config file from the admin console. Go to the realm and application you want a template for. Go to the Installation tab and this will provide you with a template that includes the public key of the realm. Here is a description of each item: realm Name of the realm representing the users of your distributed applications and services. This is REQUIRED. resource Username of the application. Each application has a username that is used when the application connects with the Keycloak server to turn an access code into an access token (part of the OAuth 2.0 protocol). This is REQUIRED. realm-public-key PEM format of public key. You can obtain this from the administration console. This is REQUIRED. auth-server-url The base URL of the Keycloak Server. All other Keycloak pages and REST services are derived from this. It is usually of the form https://host:port/auth This is REQUIRED. ssl-not-required Ensures that all communication to and from the Keycloak server from the adapter is over HTTPS. This isOPTIONAL. The default value is false meaning that HTTPS is required by default. user-resource-role-mappings If set to true, the adapter will look inside the token for application level role mappings for the user. If false, it will look at the realm level for user role mappings. This isOPTIONAL. The default value isfalse. enable-cors This enables CORS support. It will handle CORS preflight requests. It will also look into the access token to determine valid origins. This isOPTIONAL. The default value isfalse. cors-max-age If CORS is enabled, this sets the value of the Access-Control-Max-Age header. This isOPTIONAL. If not set, this header is not returned in CORS responses. cors-allowed-methods If CORS is enabled, this sets the value of the Access-Control-Allow-Methods header. This should be a JSON list of strings. This isOPTIONAL. If not set, this header is not returned in CORS responses. bearer-only This tells the adapter to only to bearer token authentication. That is, it will not do OAuth 2.0 redirects, but only accept bearer tokens through the Authorization header. This isOPTIONAL. The default value isfalse. expose-token Iftrue, an authenticated browser client (via a Javascript HTTP invocation) can obtain the signed access token via the URLroot/k_query_bearer_token. This isOPTIONAL. The default value isfalse. credentials Specify the credentials of the application. This is an object notation where the key is the credential type and the value if the value of the credential type. Currently only password is supported. This isREQUIRED. connection-pool-size Adapters will make separate HTTP invocations to the Keycloak Server to turn an access code into an access token. This config option defines how many connections to the Keycloak Server should be pooled. This isOPTIONAL. The default value is 20. disable-trust-manager If the Keycloak Server requires HTTPS and this config option is set to true you do not have to specify a truststore. While convenient, this setting is not recommended as you will not be verifying the host name of the Keycloak Server. This isOPTIONAL. The default value is false. allow-any-hostname If the Keycloak Server requires HTTPS and this config option is set to true the Keycloak Server's certificate is validated via the truststore, but host name validation is not done. This is not a recommended. This seting may be useful in test environments This isOPTIONAL. The default value is false. truststore This setting is for Java adapters. This is the file path to a Java keystore file. Used for outgoing HTTPS communications to the Keycloak server. Client making HTTPS requests need a way to verify the host of the server they are talking to. THis is what the trustore does. The keystore contains one or more trusted host certificates or certificate authorities. You can create this truststore by extracting the public certificate of the Keycloak server's SSL keystore. This is OPTIONAL if ssl-not-required is false or disable-trust-manager istrue. The default value isfalse. truststore-password Password for the truststore keystore. This is REQUIRED if truststore is set. client-keystore Not supported yet, but we will support in future versions. This setting is for Java adapters. This is the file path to a Java keystore file. This keystore contains client certificate for two-way SSL when the adapter makes HTTPS requests to the Keycloak server. This isOPTIONAL. client-keystore-password Not supported yet, but we will support in future versions. Password for the client keystore. This is REQUIRED if client-keystore is set. client-key-password Not supported yet, but we will support in future versions. Password for the client's key. This is REQUIRED if client-keystore is set.