Update from SAP DITA CMS (squashed):

commit 9794cb80669dff4a83e55989688b269105617ac0
Author: REDACTED
Date:   Wed Nov 13 10:23:21 2024 +0000

    Update from SAP DITA CMS 2024-11-13 10:23:21

    Project: dita-all/aqd1698149070184
    Project map: beff08357c9a409b9e181982b3174d9a.ditamap
    Output: loio8ba818df56c848cb808b6d698ed01afe
    Language: en-US
    Builddable map: 104367d9dc224fe7a6c407e498877d64.ditamap

commit 85cb8ecc37abe748c65dcd5e87e6bef88a97486a
Author: REDACTED
Date:   Wed Nov 6 12:36:44 2024 +0000

    Update from SAP DITA CMS 2024-11-06 12:36:44
    Project: dita-all/aqd1698149070184
    Project map: beff08357c9a409b9e181982b3174d9a.ditamap
    Output: loio8ba818df56c848cb808b6d698ed01afe
    Language: en-US
    Builddable map: 104367d9dc224fe7a6c407e498877d64.ditamap

commit 504aa1d4d158e413f7664d60842620bf9a0df80f
Author: REDACTED
Date:   Wed Nov 6 10:37:14 2024 +0000

    Update from SAP DITA CMS 2024-11-06 10:37:14
    Project: dita-all/aqd1698149070184
    Project map: beff08357c9a409b9e181982b3174d9a.ditamap
    Output: loio8ba818df56c848cb808b6d698ed01afe
    Language: en-US

##################################################
[Remaining squash message was removed before commit...]

Author: ditaccms-bot

docs/admin-and-ops/bind-a-service-instance-0aead0c.md

@@ -10,7 +10,7 @@ Bind a SAP Credential Store instance to your Cloud Foundry or Kyma application t
 
 ## Prerequisites
 
--   You've created a service instance for SAP Credential Store. See: [Create a Service Instance](create-a-service-instance-dc5f087.md)
+-   You've [created a service instance](create-a-service-instance-dc5f087.md) for SAP Credential Store.
 
 -   You've downloaded and installed the [Cloud Foundry command line interface](https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/4ef907afb1254e8286882a2bdef0edf4.html) \(cf CLI\).
 
@@ -127,7 +127,7 @@ To find them in the cockpit, open *Environment Variables* and see:
 **Related Information**  
 
 
-[Enable, Disable and Delete Service Bindings](enable-disable-and-delete-service-bindings-eb06422.md "Manage the bindings related to your SAP Credential Store service instance.")
+[Enable, Disable and Delete a Service Binding](enable-disable-and-delete-a-service-binding-eb06422.md "Manage the service bindings related to your SAP Credential Store service instances.")
 
 [Access Control Lists](../security/access-control-lists-81a9cb6.md "In SAP Credential Store, access control lists define the access (assignment) of a service binding to particular groups of credentials on a subaccount or namespace level.")
 

docs/admin-and-ops/create-a-service-instance-dc5f087.md

@@ -37,15 +37,21 @@ You can create a service instance in two ways:
 
 ## Procedure
 
-1.  From the *Credential Store* tile, choose *Create*.
+1.  Select the *Credential Store* tile and then choose *Create*.
 
-2.  Select a service plan \(**free**, **standard**, or **proxy**\).
+    > ### Tip:  
+    > Alternatively, you can go to your space, navigate to *Services* \> *Service Marketplace*, and from the upper right corner choose *Create* \> *Service Instance*.
 
-3.  Enter a name for your service instance. For example: **mycredstore**
+2.  Select a service plan \(*trial*, *free*, *standard*, or *proxy*\).
+
+    > ### Note:  
+    > Use the *proxy* plan only if you want to share your service instance with other subaccounts or spaces. See: [Create a Proxy Service Instance](https://help.sap.com/docs/credential-store/sap-credential-store/sharing-service-instances-cockpit?version=Cloud#create-a-proxy-service-instance)
+
+3.  Enter a name for your service instance.
 
 4.  Choose *Next* to set additional parameters, or *Create* to directly create your service instance.
 
-5.  To see your newly created instance, choose ![](images/Actions_62e6f79.png) \(*Actions*\) and then *Instances and Subscriptions*.
+5.  You can see your newly created instance in your space, by navigating to *Services* \> *Instances*.
 
 6.  As a next step, you can bind your service instance to an application. See: [Bind a Service Instance](bind-a-service-instance-0aead0c.md)
 

docs/admin-and-ops/create-and-delete-a-namespace-401b20c.md

@@ -1,5 +1,7 @@
 <!-- loio401b20ca5b4c46d28e97563d9577b6d6 -->
 
+<link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
+
 # Create and Delete a Namespace
 
 To create and use any kind of credentials, you first need to create a namespace.
@@ -12,7 +14,7 @@ To create and use any kind of credentials, you first need to create a namespace.
 
 -   You've enabled SAP Credential Store for your subaccount on your Cloud Foundry or Kyma space. See: [Initial Setup](../initial-setup-d5f1ce7.md) 
 
--   You've created a service instance for SAP Credential Store. See: [Create a Service Instance](create-a-service-instance-dc5f087.md)
+-   You've [created a service instance](create-a-service-instance-dc5f087.md) for SAP Credential Store.
 
 
 
@@ -25,33 +27,44 @@ Follow the steps below to create one or multiple namespaces for your service ins
 
 ## Procedure
 
-1.  From the left-side navigation menu, choose *Services* \> *Instances*.
+1.  In the SAP BTP cockpit, navigate to your subaccount and space.
+
+2.  From the left-side navigation menu, choose *Services* \> *Instances*.
 
-2.  Select a *Credential Store* instance.
+3.  Select a *Credential Store* instance.
 
-3.  From the left-side navigation menu, choose *Credential Store*.
+4.  From the left-side navigation menu, choose <span style="color:#ffffff;"><span class="SAP-icons-V5"></span></span> \(Credential Store\).
 
-4.  In the default table are listed all the namespaces you have already created, if any. To create a new one, choose *Create Namespace*.
+5.  In the default table are listed all the namespaces you have already created, if any. To create a new one, choose *Create Namespace*.
 
-5.  As a first step, you need to create a credential within the new namespace. Thus, choose a credential type \(**Password**, **Key**, or **Keyring**\) and then *Next*.
+6.  As a first step, you need to create a credential within the new namespace. Choose a credential type \(**Password**, **Key**, or **Keyring**\) and then *Next*.
 
-6.  Enter a name for your new namespace.
+7.  Enter a name for your new namespace.
 
-7.  Enter a credential name.
+8.  Enter a name for your first credential.
 
-8.  You can manually enter a credential value or let the wizard generate one for you.
+9.  You can manually enter a credential value or let the wizard generate one for you.
 
     If you choose to generate, proceed as follows, depending on the credential type:
 
     -   *Password* – to generate a password, you need to set its length, which must be at least 8 and no longer than 4096 symbols. Also, when the creation is done, the generated password **hash** \(not its real value\) will be displayed for you. Copy the provided string and keep it at a safe place so you can use it later. The hash string is always 60 symbols, regardless of the actual length of your generated password.
-    -   *Key* – to generate a key, you need to set its size, which must be at least 16 and no longer than 128 bytes.
-    -   *Keyring* – to generate a keyring, you need to set its size, which must be at least 16 and no longer than 64 bytes. You also have to enter a rotation period number – between 30 and 365 days.
+    -   *Key* – to generate a key, you need to set its size, which must be at least 16 and no more than 128 bytes.
+    -   *Keyring* – to generate a keyring, you need to set its size, which must be at least 16 and no more than 64 bytes. You also have to enter a rotation period, which must be at least 30 and no more than 365 days.
+
+10. Select the initial status of your credential \(**Enabled**, **Read-only**, or **Disabled**\). You can change this setting later.
+
+11. Choose whether your credential to be modifiable or not.
+
+    > ### Note:  
+    > Once a credential is set to *Unmodifiable*, its properties cannot be further changed – except for the *Status* attribute.
+    > 
+    > Also, unmodifiable credentials can be deleted only after being disabled for at least 7 days.
 
-9.  Select the initial status of your credential \(**Enabled**, **Read-only**, **Disabled**\).
+12. \(Optional\) Enter your username so other subaccount administrators would know that this namespace and credential were created by you.
 
-10. \(Optional\) You can enter a username and some metadata, which to associate with your credential.
+13. \(Optional\) Enter some metadata that can be associated with your credential.
 
-11. Choose *Create*.
+14. Choose *Create*.
 
 
 
@@ -68,10 +81,10 @@ The new namespace appears in the table.
 
 ## Next Steps
 
-If you want to delete an obsolete namespace, choose ![](images/CS_delete_credential_32c1346.png) \(*Delete*\).
+If you want to delete an obsolete namespace, choose <span style="color:#007cc0;"><span class="SAP-icons-V5"></span></span> \(Delete\).
 
 > ### Note:  
-> If your namespace contains keyrings, they have to be in status **Disabled** and have stayed disabled for at least 7 days so you can be allowed to delete the namespace. This is a security precaution that protects your keyrings from unintentional deletion.
+> If your namespace contains keyrings, they have to be in status **Disabled** and should have stayed disabled for at least 7 days so you can be allowed to delete the namespace. This is a security precaution that protects your keyrings from unintentional deletion.
 
 **Related Information**  
 

docs/admin-and-ops/create-download-and-delete-a-service-key-7502e17.md

@@ -1,5 +1,7 @@
 <!-- loio7502e1780e5b46f7982f8cc2a37a0080 -->
 
+<link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
+
 # Create, Download, and Delete a Service Key
 
 To use a service instance from an external application or an application deployed in another space, you need to create a service key.
@@ -10,9 +12,7 @@ To use a service instance from an external application or an application deploye
 
 ## Prerequisites
 
--   You've enabled SAP Credential Store for your subaccount on your Cloud Foundry or Kyma space. See: [Initial Setup](../initial-setup-d5f1ce7.md) 
-
--   You've created a service instance for SAP Credential Store. See: [Create a Service Instance](create-a-service-instance-dc5f087.md)
+-   You've [created a service instance](create-a-service-instance-dc5f087.md) for SAP Credential Store.
 
 -   You've downloaded and installed the [Cloud Foundry command line interface](https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/4ef907afb1254e8286882a2bdef0edf4.html) \(cf CLI\).
 
@@ -37,29 +37,32 @@ You can create a service key in two ways:
 > ### Note:  
 > For newly created service keys, the default validity is **60** days. This applies to service instances with all types of authentication \(`basic`, `mtls`, `oauth:key`, and `oauth:mtls`\).
 > 
-> If you want to change the service key validity, go to the service instance and choose *Credential Store* \> *Settings* \> *Edit Configuration*.
+> If you want to change the service key validity, go to the service instance and choose *Credential Store* \> *Settings* \> *Edit Configuration* \> *Binding Validity*.
 
 
 
 ## Procedure
 
-1.  From the left-side navigation menu, choose *Services* \> *Instances*.
+1.  In the SAP BTP cockpit, navigate to your subaccount and space.
 
-2.  Select a *Credential Store* instance.
+2.  From the left-side navigation menu, choose *Services* \> *Instances*.
 
-3.  From the left-side navigation menu, choose *Service Keys*.
+3.  Select a *Credential Store* instance.
 
-4.  Choose *Create Service Key*.
+4.  From the left-side navigation menu, choose *Service Keys*.
 
-5.  Enter a name for the new service key.
+5.  Choose *Create Service Key*.
 
-6.  \(Optional\) Define configuration parameters in JSON format for this service key.
+6.  Enter a name for the new service key.
 
-    The parameters are the same as in **step 4** in task [Bind a Service Instance](bind-a-service-instance-0aead0c.md).
+7.  \(Optional\) Define configuration parameters in JSON format for this service key.
 
-7.  Choose *Save*. The service key is created.
+    The parameters are the same as in **step 5** in task [Bind a Service Instance](bind-a-service-instance-0aead0c.md).
 
-    The properties are the same as the ones in task [Bind a Service Instance](bind-a-service-instance-0aead0c.md).
+8.  Choose *Save*. The service key is created.
+
+    > ### Tip:  
+    > The relevant properties in the VCAP\_SERVICES environment variable are the same as the ones described in [Bind a Service Instance: Next Steps](https://help.sap.com/docs/credential-store/sap-credential-store/bind-service-instance?version=Cloud#next-steps).
 
 
 
@@ -68,8 +71,15 @@ You can create a service key in two ways:
 
 ## Next Steps
 
--   To download a service key, choose ![](images/CS_save_as_JSON_27dc49d.png) \(*Save JSON to file*\).
+-   To download a service key, choose <span style="color:#007cc0;"><span class="SAP-icons-V5"></span></span> \(Save JSON to file\).
+
+-   To delete an obsolete service key, choose <span style="color:#007cc0;"><span class="SAP-icons-V5"></span></span> \(Delete Service Key\).
+
+
+**Related Information**  
+
 
--   To delete an obsolete service key, choose ![](images/CS_delete_credential_32c1346.png) \(*Delete Service Key*\).
+[Bind a Service Instance](bind-a-service-instance-0aead0c.md "Bind a SAP Credential Store instance to your Cloud Foundry or Kyma application to enable the automatic delivery of credentials needed to access the service instance from this application.")
 
+[Cloud Foundry: VCAP\_SERVICES](https://docs.cloudfoundry.org/devguide/deploy-apps/environment-variable.html#VCAP-SERVICES)