question

PatriceCt-1547 avatar image
0 Votes"
PatriceCt-1547 asked PatriceCt-1547 commented

Testing seemless migration to Azure AD B2C

We are moving from an on prem identity provider to Azure AD B2C. Based on this official Microsoft documentation, we decided to go with the seemless migration process. The only problem I have with this approach is that we cannot really test it until we are in production, because our api's route that needs to be called (to validate user's credentials against legacy idp) are not reachable from the outside in all development/integration stages (for obvious reasons).

I want to know if anyone has ever implemented this flow in real life and if so, how did you manage to test it?


azure-ad-b2c
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AlfredoRevilla avatar image
2 Votes"
AlfredoRevilla answered PatriceCt-1547 commented

Hi @patricect-1547, you can mock your legacy API responses using API Management. Additionally, you can build a mocked API and deploy it to Azure App Services and use it as a standalone backend or behind API Management. Or finally, if your company allows it, you can make your private APIS available through API Management.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I like the idea of mocking in Azure. Thanks for the suggestion @AlfredoRevilla !

0 Votes 0 ·
sikumars avatar image
0 Votes"
sikumars answered

Hello @PatriceCt-1547,

Thanks for reaching out.

I hope suggestion which provided over here helpful, if you have any additional queries, please let us know. Thanks.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.