Iulian C.
Iulian C.
@v-npadhy , can you pls share your code a screenshot of the prompt you are seeing when accessing resource_id2.
MSAL.runtime currently doesn't support combined consent. This would be a feature ask. For now, please request tokens interactively for each necessary scope.
This feature is currently not scheduled for execution, but we can add it to our backlog and prioritize it based on all other asks we get.
Closing as workaround exists and the reported problem not being supported by CIAM.
Do the MSA and AAD account have the same UPN ?
@50Wliu, in general this behavior looks by design GetAccountsAsync() returns all accounts that are available on the system not only the accounts that application previously sign-ed in with.
@rayluo, Error corresponding to tag "tag_4sh5j - Wam returned default account that doesn't match the account passed in" is an t optimization effort where account MSAL.net passes is not found...
@matthewacme, are you trying to enable auth for native AAD auth or B2C /external ID ?
This is a known, recently discovered defect, in eSTS implementation of the protocol used by Windows broker to issue v2 tokens. We don't have a concrete timeline, but the plan...
@halbyr, please share more details on your e2e scenario. Logic that requires that client to control force prompt behavior usually indicates to a problematic calling pattern within your app.