Skip to main content

Unable to obtain an access token due to CORS policy restrictions

  • April 17, 2024
  • 6 replies
  • 0 views
S

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

6 replies

S

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

We apologise for the inconvenience.

S

@gmilcinski 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.

S

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

S

@gmilcinski here’s my client ID : 78036512-bab3-4e39…

S

It works now. Thanks a lot

S

I am getting CORS issue with “https://services.sentinel-hub.com/auth/realms/main/protocol/openid-connect/token”
my client id : af5eba7a-85ce-4d14

Terms & ConditionsCookie settingsAccessibility statement
Account
Usage and reporting
Data
Search and orderView ordersView subscriptionsView data collectionsManage areas of interestBasemaps Viewer
Analyze
BrowserConfigurationsRequest Builder
Learn
DocumentationPlanet UniversityTerms of Use
Other
ExplorerStoriesTasking DashboardFeatures Manager

© 1994 Planet Labs PBC. All rights reserved. | Privacy Policy | California Privacy Notice |
Your Privacy Choices | Cookie Notice | Terms of Use