Skip to main content

Unable to obtain an access token due to CORS policy restrictions

  • April 26, 2024
  • 6 replies
  • 131 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,
can you perhaps try again?
The issue should have been resolved about 20 minutes ago.

We apologise for the inconvenience.

S

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

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

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 : *deleted for privacy reasons*

Terms & ConditionsAccessibility statement
Planet Monitoring
Planet Tasking
Single Order Tasking
Planet Analytic Feeds
Planetary Variables
Planet Basemaps
Planet Insights Platform
Pricing
Broad Area Management
Agriculture
Science Program
Energy & Infrastructure
Forestry & Land Use
Insurance
Mapping
Sustainability
Maritime
Civil Government
US State and Local
Europe
Planet Federal
Defense & Intelligence
Armed Services
Investors
Connect with Planet Partners
Become a Partner
Planet Esri Partnership
Find a Partner
About Us
Customer Stories
Our Team
Careers
Press
Resources
Impact at Planet
Contact Us
Art at Planet
FAQs
Legal Entities
Planet University
Documentation
Help Center
Publications Database
Contact Sales
Explorer Log In
Partner Portal
Investors
Blog
Gallery
Disaster Data
Publications
Planet Insights
Planet Stories

© 2025 Planet Labs PBC. All rights reserved.
| Privacy Policy | California Privacy Notice | California Do Not Sell
Your Privacy Choices | Cookie Notice | Terms of Use