Skip to content

Commit a20e911

Browse files
Update sap-xsuaa-connector.md
1 parent e93b564 commit a20e911

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

content/en/docs/appstore/use-content/platform-supported-content/modules/sap/sap-xsuaa-connector.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ You need to provide your own [xs-security.json](https://help.sap.com/viewer/4505
6161

6262
You then have two options:
6363

64-
### Use the XSUAA Configurator {#configurator}
64+
### Using the XSUAA Configurator {#configurator}
6565

6666
The **XSUAA Configurator** provides a user friendly interface to create the JSON required to configure the XSUAA service. It can be uploaded automatically for you, or you can download the file and upload it manually.
6767

@@ -81,7 +81,7 @@ You cannot change the **xsappname** in the configurator – this is generated au
8181

8282
Alternatively, click **Download Configuration File** to save the file locally so that you can review it, or reuse it. You can upload it manually to the XSUAA service using the instructions in the next section.
8383

84-
### Upload Configuration JSON
84+
### Uploading a Configuration JSON
8585

8686
You can upload your own JSON configuration file, either created from the XSUAA Configurator or handcrafted.
8787

@@ -106,7 +106,7 @@ For more information about implementing this capability in your app, see the fol
106106
SAP Authentication will not work if the App Security is off. See the prerequisites above.
107107
{{% /alert %}}
108108

109-
### Adding the OnStartup Microflow to the Application Settings
109+
### Adding the On Startup Microflow to the Application Settings
110110

111111
The app needs to be bound to the SAP XSUAA service. This is achieved by executing a microflow when the app starts. This may have been set up already if XSUAA was included in your app template.
112112

@@ -258,7 +258,7 @@ Your Subaccount will have one or more **Trust Configurations**. These are the Id
258258

259259
Depending on the IdP, you can either map **Users** (G) directly to a Role Collection, or map a **User Group** (F) to a Role Collection. Users are mapped by the IdPs own configuration to the User Group.
260260

261-
##### Map User Directly to a Role Collection
261+
##### Mapping a User Directly to a Role Collection
262262

263263
This is the method used by the **SAP ID Service**, amongst others.
264264

@@ -275,7 +275,7 @@ You can picture the authentication as shown below:
275275

276276
{{< figure src="/attachments/appstore/platform-supported-content/modules/sap-xsuaa-connector/xsuaa-diagram-config-direct.png" class="no-border" >}}
277277

278-
##### Map User Group to a Role Collection
278+
##### Mapping a User Group to a Role Collection
279279

280280
Some IdPs (for example SAML 2.0 IdPs) have the concept of a User Group. In this case there will be two options in the Trust Configuration for the IdP: **Role Collection Mappings** and **Role Collection Assignment**.
281281

0 commit comments

Comments
 (0)