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
|**`DISABLED`**| No exchange. Each token type is validated and used as-is. |
154
-
|**`PROVIDE_XSUAA`**| IAS token is validated and exchanged for XSUAA, but the IAS token remains primary in the security context. The XSUAA token is accessible via [`SecurityContext.getXsuaaToken()`](java-api/src/main/java/com/sap/cloud/security/token/SecurityContext.java). |
155
-
|**`FORCE_XSUAA`**| IAS token is exchanged for XSUAA and the XSUAA token replaces the IAS token in the security context. The application treats all requests as XSUAA-authenticated. |
|**`DISABLED`**| No exchange. Each token type is validated and used as-is. |
154
+
|**`PROVIDE_XSUAA`**| IAS token is validated and exchanged for XSUAA, but the IAS token remains primary in the security context. The XSUAA token is accessible via [`SecurityContext.getXsuaaToken()`](java-api/src/main/java/com/sap/cloud/security/token/SecurityContext.java). |
155
+
|**`FORCE_XSUAA`**| IAS token is exchanged for XSUAA and the XSUAA token replaces the IAS token in the security context. The resulting security context looks as if an XSUAA token had been received directly. |
156
+
157
+
The Initial token is still available via the [`SecurityContext.getInitialToken()`](java-api/src/main/java/com/sap/cloud/security/token/SecurityContext.java) getter and the ID token is available with [`SecurityContext.getIdToken()`](java-api/src/main/java/com/sap/cloud/security/token/SecurityContext.java)
156
158
157
159
**Mode Selection Guide**:
158
160
159
-
- Use **`PROVIDE_XSUAA`** when gradually building IAS-based features while maintaining XSUAA authorization
160
-
- Use **`FORCE_XSUAA`** for maximum backward compatibility—your app operates as if it were XSUAA-only
161
-
- Use **`DISABLED`** after completing the migration to IAS
161
+
- Use **`PROVIDE_XSUAA`** when the app is migrated to AMS authorization and wants to offer combined XSUAA and AMS authorizations for migrated tenants (requires additional configuration of the AMS client library)
162
+
- Use **`FORCE_XSUAA`** for maximum backward compatibility—the app operates based on XSUAA tokens like before
163
+
- Use **`DISABLED`**or remove the property completely after completing the migration to IAS
162
164
163
165
#### Prerequisites for Token Exchange
164
166
165
167
1. Both XSUAA and IAS service bindings must be configured
166
-
2. IAS service binding must include `xsuaa-cross-consumption: true` parameter (Cloud Foundry)
167
-
3.On Kubernetes/Kyma, ensure XSUAA trusts the IAS identity provider
168
+
2. IAS service binding must include `xsuaa-cross-consumption: true` parameter
0 commit comments