token_endpoint request fails to fetch response

[Naveenbc]

token_enpoint request fails to fetch response but when I try in postman with same configuration it is working.

My index.tsx looks like the below

const oidcConfig = { authority: authority_url, client_id: "5afa1a2b-9ab1-424b-80a3-b826ba3b8c79", redirect_uri: window.location.origin, metadata: { issuer: "issurer url", authorization_endpoint: "", token_endpoint: "", userinfo_endpoint: "" }, response_type: "code", scope: "openid entitlement_group authorization_group location_data profile", post_logout_redirect_uri: "", filterProtocolClaims: true // ... };

const root = ReactDOM.createRoot( document.getElementById('root') as HTMLElement ); root.render( <React.StrictMode> <AuthProvider {...oidcConfig}> <AppAuth /> </AuthProvider>

</React.StrictMode> );

kindly help.

Thanks, Naveen B C

[pamapa]

Works here reliable, you need to find out why its not working on your side. Is the token_endpoint URL correct? ...

You should not provide the metadata, unless you really need. If not provided the underlying library oidc-client-ts will fetch that information automatically by default from authority/.well-known/openid-configuration. In case one metadata url is wrong or missing you can use metadataSeed.

[Naveenbc]

CORS is not enabled in my Authority URL, So it is necessary to give metadata information. I have cross checked the urls, it is fine. Kindly give me more information on metadata seed.

Also only difference I see in our token end point call and postman's token end point call is presence of "authorization": "Basic NWFmYTFhMmItOWFiMS00MjRiLTgwYTMtYjgyNmJhM2I4Yzc5Og==", in request headers in postman's call and not in our request call.

[pamapa]

Also only difference I see in our token end point call and postman's token end point call is presence of "authorization": "Basic NWFmYTFhMmItOWFiMS00MjRiLTgwYTMtYjgyNmJhM2I4Yzc5Og==", in request headers in postman's call and not in our request call.

I guess that is your problem. You can instruct oidc-client-ts to pass that too. See settings.client_authentication + settings.client_secretin the settings or code...