Current situation
I have an ADB2C server with these settings:
- A custom User Attribute
InstancesAvailablewas created - This user attribute is set to be returned as an Application claims in in my “Sign up and sign in (Recommended)” user flow
- An API connector is defined to be executed “Before including application claims in token (preview)” in the user flow
- My API endpoint defined to be called from the API connector is returning an
extension_InstancesAvailableproperty, to be added as a claims in the bearer token produced by the Identity server
All of that is working, the typical use case is:
- A user signs in to my React web app using MSAL and the above user flow defined in ADB2C
- During the sign-in process, my API endpoint is thus called for constructing and returning the custom
extension_InstancesAvailableclaims value to be added by the Identity server - Once the user gets signed into my application, his bearer token correctly includes the
extension_InstancesAvailableclaims value
Question
I am thinking forward: There will be an action available in my web application to “add a new instance”. Since the list of available instances is forged into the bearer token during the sign-in, is there a way to “regenerate” the bearer token of a user, without having to sign-out/sign-in or even re-enter password?
Ideally, I would like to regenerate the bearer token after a specific action is done inside my web app, so the extension_InstancesAvailable contains the correct list, including the one just created by the user.


