@BCTAZURE
Thank you for your post and I apologize for the delayed response!
When it comes to using Azure B2C to connect to an external database to validate a user's Username/ ID and Password, you should be able to achieve this through the use of the API connectors custom policy.
Use API connectors to customize and extend sign-up user flows and custom policies with external identity data sources:
Using Azure AD B2C, you can add your own business logic to a user journey by calling your own RESTful service. The Identity Experience Framework can send and receive data from your RESTful service to exchange claims. For example, you can:
- Use external identity data source to validate user input data. For example, you can verify that the email address provided by the user exists in your customer's database, and if not, present an error. You can as well think of API connectors as a way of supporting outbound webhooks because the call is made when an event occurs, for example, a sign up.
Here's an example of the steps take:
- Create a RESTful API that can validate user credentials against your external database.
For more info - Development of your REST API.
- Define a technical profile in your custom policy that calls your RESTful API to validate user credentials.
For more info - Define a RESTful technical profile in an Azure B2C custom policy.
- Add the technical profile to your user journey to enable users to sign in using your custom policy.
For more info - UserJourneys.
Additional Links:
I hope this helps!
If you have any other questions, please let me know. Thank you for your time and patience throughout this issue.
If the information helped address your question, please Accept the answer. This will help us and also improve searchability for others in the community who might be researching similar information.