fix(jans-linux-setup): improper scim configuration for jans kc #8210

* updated the keycloak configuration file to reflect the  configuration for the storage-spi

Signed-off-by: Rolain Djeumen <uprightech@gmail.com>

jans-linux-setup/jans_setup/templates/jans-saml/keycloak.conf

@@ -41,22 +41,23 @@
 
 # Janssen configuration parameters
 
-# Storage spi configuration 
+# Storage SPI Configuration (SCIM)
 
-# token endpoint 
-#jans-storage-auth-token-endpoint=
+# janssen-auth token endpoint 
+spi-storage-kc-jans-storage-auth-token-endpoint=
 
-# scim user endpoint
-#jans-storage-scim-user-endpoint
+# janssen scim user fetch endpoint 
+# usually of the format https://<server>/jans-scim/restv1/v2/Users
+spi-storage-kc-jans-storage-scim-user-endpoint=
 
 # scim user search endpoint 
-#jans-storage-scim-user-search-endpoint
+spi-storage-kc-jans-storage-scim-user-search-endpoint=
 
 # scim oauth scopes
-#jans-storage-scim-oauth-scope
+spi-storage-kc-jans-storage-scim-oauth-scopes=https://jans.io/scim/users.read https://jans.io/scim/users.write
 
 #scim client id 
-#jans-storage-client-id
+spi-storage-kc-jans-storage-scim-client-id=
 
 #scim client secret
-#jans-storage-client-secret
+spi-storage-kc-jans-storage-scim-client-secret=