Azure AD B2C. ROPC flow error The application associated with client id has no registered redirect URIs

Question

The application associated with client id 09ac92da-a796-4cd9-973b-c97756____ has no registered redirect URIs

Description

I followed the steps described in https://docs.microsoft.com/en-us/azure/active-directory-b2c/configure-ropc?tabs=applications.

When attempting to obtain the token in Postman using ROPC I'm getting

{
    "error": "invalid_request",
    "error_description": "AADB2C90007: The application associated with client id '09ac92da-a796-4cd9-973b-c97756____' has no registered redirect URIs.\r\nCorrelation ID: e85003c3-cfd5-43ad-a74b-efa5c1ea6525\r\nTimestamp: 2019-12-06 19:47:42Z\r\n"
}

I should not be asked for a redirect URIs.

My POST is as follows:

URL: ''https://mytenant.b2clogin.com/mytenant.onmicrosoft.com/oauth2/v2.0/token?p=B2C_1_ROPC_Auth"

username: some_username_of_a_user
password: its-password
grant_type: password
scope: openid offline_access 09ac92da-a796-4cd9-973b-c97756____
client_id: 09ac92da-a796-4cd9-973b-c97756____
response-type: token id_token

Answer 1

This error generally occurs because you still need to configure some application claims in the b2c directory user flow to allow complete access to the application.

You need to make sure that the right versions of the authentication are in the reply url (likely extension v2.0) and that the reply URL is configured in the application and in the code.

Please look to the documentation for the reply URL schema that you would need to follow: https://docs.microsoft.com/en-us/azure/active-directory-b2c/tutorial-register-applications?tabs=applications#register-a-web-application

If you still run into this issue let me know and I can reach out to the correct product team contacts, as sometimes this can happen due to breaking changes on our end.

Answer 2

I didn't reproduce your issue by following this document. Here are the main steps for your reference.

1.Create a resource owner user flow

2.Register an application(It is an application under Azure AD B2C, not Azure AD)

3.Test the user flow