Arrays in nested token get converted to special characters /r/n in when it is passed through B2C. Please advise on timeline for arrays to be supported in B2C with no special characters. MS tkt # 120110624005531 has been raised for the same
Arrays in nested token get converted to special characters /r/n in when it is passed through B2C. Please advise on timeline for arrays to be supported in B2C with no special characters. MS tkt # 120110624005531 has been raised for the same
Thanks @MellacheruvuSrivalli-0510. Could you please follow the document mentioned - https://docs.microsoft.com/en-us/azure/active-directory-b2c/api-connectors-overview?pivots=b2c-custom-policy
and also make sure, please use the following meta data in the technical profile processing a json response:
<Item Key="ResolveJsonPathsInJsonTokens">true</Item>
This does not satisfy our needs. Hence we have written custom b2C policy instead of API connector.
@MellacheruvuSrivalli-0510
Thank you for your post!
From your support request concerning Cosmos DB and Azure B2C id_tokens. Our Azure B2C PG team provided an update saying that this is unsupported and is currently not on their Azure B2C Roadmap. You were then redirected here to create a feature request on Microsoft Q&A so others in the community can up vote this thread.
I've passed this along to our engineering team and will update as needed. Additionally, I'd recommended continuing to use our User Voice forum for feature requests so our engineering team can take a look into implementing this.
Thank you for your time and patience throughout this issue.
Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.
3 people are following this question.