Symptom
- If no credential types are defined in the application security descriptor, the SAP Authorization and Trust Management service applies a default value .
- This default value will be changed to binding-secret (instead of instance-secret). As per What's New for SAP Business Technology Platform.
- As part of the new change, below code will be added in XS-Security.json file,
"oauth2-configuration": {
"token-validity": 3600,
"credential-types": [
"binding-secret",
"x509"
]
},
"xsenableasyncservice":"true", - For every deployment Client Secret is changing due to which user have to update the destination in BTP to make API to work.
- Is there any other parameter which will stop creating new secret for every deployment?
Read more...
Environment
- SAP BTP, Cloud Foundry runtime and environment
Product
SAP BTP, Cloud Foundry runtime and environment all versions
Keywords
Change of Default Credential Type to binding-secret, Authorization and Trust Management Service, XS-Security.json, XS-Security.json file, deployment, destination, update, client secret, binding-secret, BTP, security, Binding secrets, service key, binding, credential, instance secret type, xs-security json, BTP-UAA-0003, BTP-UAA-0004. , KBA , BC-CP-CF-SEC-IAM , UAA, Authentication, Authorization, Trust Mgmnt , BC-CP-CF-CPT , SAP BTP Cockpit - Cloud Foundry environment UI , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview