Not getting access token

[timduncan-innowell]

Hi,

After downloading the b2c-sample application and making config changes for my B2C tenant, I cannot get an access token back from getTokensAsync().

Here is my config:

<AuthProvider
         tenant="myapp"
         appId="<appId>"
         loginPolicy="B2C_1A_signin"
         passwordResetPolicy="B2C_1A_PASSWORD_RESET"
         profileEditPolicy="B2C_1_ProfleEdit"
         redirectURI="msauth://com.myapp/<signature_hash>"
>

I correctly get the B2C hosted signin page after clicking the LOGIN button. After entering a correct user name and password the Protected page displays "Could not authenticate".

What I do get from getTokensAsync() is:

{
  "access": "", 
  "error": null, 
  "expiresOn": 0, 
  "id": "", 
  "isAuthentic": false, 
  "url": "msauth://com.myapp/<signature_hash>?code=eyJraWQiOiIxVG9LRlVnM1lVNE9ET1lJbz..." 
}

The url seems to be the first part of the authorization code flow and afaik the package should be exchanging the authorization code for access & id tokens. The exchange does not seem to take place.

Have I done something wrong to stop the authorization code from being processed by the package and used in a token exchange?

Any help appreciated.

[harika-nammi]

hi @timduncan-innowell, i am also facing the same issue. Did you fix this?

[MuhammadSaadTabani]

Facing the same issue, I ask from community developers to kindly help with the solution. Thank you

[GSingh01]

@timduncan-innowell to me it looks like you are not being redirected to correct link for your app. Can you please put a breakpoint or console.log at

ad-b2c-react-native/packages/b2c-sample/App.tsx

Line 31 in 8327ea3

redirectURI={Linking.createURL("redirect")}

to read the value of Linking.createURL("redirect") and this is what you need to put in Azure ad b2c redirect url config for dev env.

Note: In prod, above will be different and will depend upon on schema in app config. More about it here: https://docs.expo.dev/versions/latest/sdk/linking/#linkingcreateurlpath-namedparameters

[MuhammadSaadTabani]

Everything is working correctly, we are able to signin, but not getting access token. we are getting error:null and isAuthentic false.

[GSingh01]

@MuhammadSaadTabani there are 2 parts to it

1. Making request to load Login screen
2. Loading the application and authenticating after receiving redirect from ad b2c

When you refer everything is working my guess is you are referring to number 1 but unless number 2 is done you wont be authenticated.

To make sure you can put a breakpoint at redirect route and double check if it ever gets hit, if not check my initial comment. If it gets hit and you still dont see it working then please provide more info what the error code etc you are getting.

[MuhammadSaadTabani]

Yeah I am facing the following issues, kindly have a look at.

1. when I am using Liking.createURI(''), I am getting the following response and couldn't see the login page from azure auth.

Object {
    access: "",
    error: "dismiss",
    expiresOn: 0,
    id: "",
    isAuthentic: false,
    url: ""
}

2. When I am passing redirect uri direct string to redirectURI prop, I am able to see the login page and easily sign in to the application, but I am not getting access-token in the repsonse, the error is null by the way and isAuthentic is false, following is the response after login to the app

access: "",
error: null,
expiresOn: 0,
id: "",
isAuthentic: false,
url: msauth://someurl...

Auth Provider Configuration

<AuthProvider
        tenant={'<app-tenant>'}
        appId={'<my-app-id>'}
        loginPolicy="<login-policy>"
        passwordResetPolicy="<password-reset-policy>"
        scope={['openid', 'offline_access' ]}
        redirectURI={Linking.createURL('redirect-uri')}
>

[timduncan-innowell]

@GSingh01 ,

Thanks for responding.

My current redirectURI msauth://com.myapp/<signature_hash> was configured from adding an Android platform (other options are Web, Single-page application, iOS / macOS, Mobile and desktop applications). Is Android the right platform for a React Native application?

Now, looking at the expo Linking documentation as you suggested I see this example value when running in dev environment:

Expo Client (dev): exp://128.0.0.1:19000/--/path

My understanding from your response is that I should change my redirectURI in the portal to be exp://128.0.0.1:19000/--/redirect, correct?