Problem with XSUAA service in XS Advanced

[Former Member]

Description: We use mta deployment with XSUAA service. Service is defined in mta in resource section as following: - name: <app_name> type: com.sap.xs.uaa parameters: config-path: ./xs-security.json After upgrading XSA version from <1.0.64> to <1.0.84> we experienced following issues: 1. service-plan after redeploy was set to default. 2. client_id is auto-generated <na-9f6d9f5e-42fd-4579-be2a-7a85e1dc1b5f!u1> (we know this is consequence of default plan) 3. xs security json is not loaded (missing scopes and templates) We added service plan parameter to mta and now we have dev-user plan as expected but xs-security config is still missing. Also we noticed that xsappname is generated (something like na-9f6d9f5e-42fd-4579-be2a-7a85e1dc1b5f!u1)

Are we missing something else in parameters section?

[thomas_jung]

I don't think the deployer can change such base parameters for the UAA after deployed. Have you tried manually deleting the UAA before you deploy again?

[Former Member]

Hi Thomas,

When service is deleted and created manually everything is fine. XSAPPNAME, CLIENTID have proper name and also we are able to create role collections.
If deleted before deploy, same problems occurs. Only if manualkly delted and created it is ok.

[thomas_jung]

Are you building the MTA from the Web IDE? If so, referencing the xs-security.json file doesn't work because it unfortunately doesn't get packed into the MTAR file. You can confirm this by opening the MTAR file with a zip utility. Instead you have to in-line the xs-security.json file contents into the mta.yaml. An example of this is available here: https://github.com/SAP/com.sap.openSAP.hana5.example/blob/hana2_sps03/mta.yaml

Notice that in the UAA resource description, the xs-security.json details are exploded in-line.

[Former Member]

Hi Thomas,

That helped. It is working now. Thank you a lot!