Update docs_user/modules/proc_adopting-the-identity-service.adoc

Co-authored-by: Katie Gilligan <[email protected]>

Author: xek

docs_user/modules/proc_adopting-the-identity-service.adoc

@@ -135,20 +135,12 @@ $ oc create secret generic keystone-domains \
   -n <namespace> \
   --from-file=<keystone.DOMAIN_NAME.conf>
 ----
-
-After creating the secret, you would typically remove the local configuration file if it's no longer needed or store it securely.
-
-IMPORTANT: The name of the file provided to `--from-file` (e.g., `keystone.DOMAIN_NAME.conf`) is critical. Keystone uses this filename to map incoming authentication requests for a domain to the correct LDAP configuration. Ensure `DOMAIN_NAME` matches the name of the domain you are configuring in Keystone.
-
-If you have multiple LDAP domains, create a configuration file for each (e.g., `keystone.DOMAIN_ONE.conf`, `keystone.DOMAIN_TWO.conf`). Then, create the secret with all files:
-[source,bash]
-----
-oc create secret generic keystone-domains \
-  -n <namespace> \
-  --from-file=keystone.conf.ldap.DOMAIN_ONE \
-  --from-file=keystone.conf.ldap.DOMAIN_TWO
-----
-
++
+* Replace `<namespace>` with the namespace where your {identity_service} is deployed.
+* Replace `<keystone.DOMAIN_NAME.conf>` with the name of your local configuration file. If applicable, include additional configuration files by using the `--from-file` option. After creating the secret, you can remove the local configuration file if it is no longer needed, or store it securely.
++
+[IMPORTANT]
+The name of the file that you provide to `--from-file`, for example `keystone.DOMAIN_NAME.conf`, is critical. The {identity_service} uses this filename to map incoming authentication requests for a domain to the correct LDAP configuration. Ensure that `DOMAIN_NAME` matches the name of the domain you are configuring in the {identity_service}.
 
 .Patch the OpenStackControlPlane CR