Skip to main content

Unable to obtain an access token due to CORS policy restrictions

  • 26 April 2024
  • 6 replies
  • 10 views

I’m unable to obtain an access token due to the CORS policy, even after creating a new OAuth2 client from the Dashboard and implementing the necessary JavaScript updates during migration.


image

Dear,
can you perhaps try again?
The issue should have been resolved about 20 minutes ago.

We apologise for the inconvenience.


thank you for your replay
I still to encounter the same issue, and I’m seeking a solution. If there’s any recommended approach to address and resolve this problem, I would appreciate guidance.


Can you please provide the first three blocks of your client ID, so that we check?


here’s my client ID :*deleted for privacy reasons*


It works now. Thanks a lot


I am getting CORS issue with “https://services.sentinel-hub.com/auth/realms/main/protocol/openid-connect/token
my client id : *deleted for privacy reasons*


Reply