The xsuaa service config uses a static xsappname, which may lead to manual errors or deployment errors, even though its mentioned in the tutorial. The phrase "You added the name of your application in the attribute xsappname and declared a role collection to which you can assign users later." might be misleading.
So instead of manually inserting the xsappname in xs-security.json, you could use the placeholder ${xsappname} as its already defined in the mta.yaml under parameters -> xsappname: bookstore-${org}-${space}.
In xs-security.json:
{
"xsappname": "${xsappname}",
...
}
Hope this helps, could reduce manual errors when users change their Org or Space names.
Tutorials: https://developers.sap.com/tutorials/cp-cap-java-deploy-cf.html
The xsuaa service config uses a static xsappname, which may lead to manual errors or deployment errors, even though its mentioned in the tutorial. The phrase "You added the name of your application in the attribute xsappname and declared a role collection to which you can assign users later." might be misleading.
So instead of manually inserting the xsappname in xs-security.json, you could use the placeholder ${xsappname} as its already defined in the mta.yaml under parameters -> xsappname: bookstore-${org}-${space}.
In xs-security.json:
Hope this helps, could reduce manual errors when users change their Org or Space names.