We have two applications A and B running on the same server.
The id_token of each application represents a different aspect of the same user. They should not be used interchangeably.
However, when a user opens both applications in the same browser, id_token of application A might be send to application B (which leads to failure).
We cannot use sub-domains (as the applications are embedded into another application, which runs on a single domain).
It would help if local storage entries such as id_token, would be scoped, like this:
appA.id_token
appA.id_token_expiration
...
appB.id_token
appB.id_token_expiration
...
This would require a configuration for the scope / prefix / app name and some sort of indirection when accessing Storage.
We looked into the uaa-authentication-client code and came to the conclusion, that any effort from our side would be hacky and / or require rewriting larger parts of the client.
What would it entail for the A12-team to make this feature part of the product?