You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/appstore/use-content/platform-supported-content/modules/sap/sap-xsuaa-connector.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ You need to provide your own [xs-security.json](https://help.sap.com/viewer/4505
61
61
62
62
You then have two options:
63
63
64
-
### Use the XSUAA Configurator {#configurator}
64
+
### Using the XSUAA Configurator {#configurator}
65
65
66
66
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.
67
67
@@ -81,7 +81,7 @@ You cannot change the **xsappname** in the configurator – this is generated au
81
81
82
82
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.
83
83
84
-
### Upload Configuration JSON
84
+
### Uploading a Configuration JSON
85
85
86
86
You can upload your own JSON configuration file, either created from the XSUAA Configurator or handcrafted.
87
87
@@ -106,7 +106,7 @@ For more information about implementing this capability in your app, see the fol
106
106
SAP Authentication will not work if the App Security is off. See the prerequisites above.
107
107
{{% /alert %}}
108
108
109
-
### Adding the OnStartup Microflow to the Application Settings
109
+
### Adding the On Startup Microflow to the Application Settings
110
110
111
111
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.
112
112
@@ -258,7 +258,7 @@ Your Subaccount will have one or more **Trust Configurations**. These are the Id
258
258
259
259
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.
260
260
261
-
##### Map User Directly to a Role Collection
261
+
##### Mapping a User Directly to a Role Collection
262
262
263
263
This is the method used by the **SAP ID Service**, amongst others.
264
264
@@ -275,7 +275,7 @@ You can picture the authentication as shown below:
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**.
0 commit comments