Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use HERE apiKey v3 instead of legacy app_id and app_code #342

Closed
mcguffin opened this issue Dec 21, 2019 · 3 comments · Fixed by #343
Closed

Use HERE apiKey v3 instead of legacy app_id and app_code #342

mcguffin opened this issue Dec 21, 2019 · 3 comments · Fixed by #343

Comments

@mcguffin
Copy link
Contributor

I cannot generate an app_id / app_code pair in my (freshly generated) HERE account any more, they seem to have switched to a single apiKey authorization.
https://developer.here.com/documentation/map-tile/dev_guide/topics/quick-start-map-tile.html

I would gladly craft a PR to fix this, but I am not sure, if *.maps.api.here.com with app_id and app_code is still functional. Does anyone have more intel on this?
@brunob
Copy link
Member

brunob commented Dec 21, 2019

Thx for the PR proposition :)

Sorry, i don't have any info about here usage from my side...

@mcguffin
Copy link
Contributor Author

I just asked in HEREs slack channel. Lets hope they have answers...

@mcguffin mcguffin mentioned this issue Jan 10, 2020
Merged
@mcguffin
Copy link
Contributor Author

No answer from HER yet ... anyway, some people on slack still seem to use app_id and app_code, so I posted a non-destructive PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Introduce HEREv3 (using apiKey instead of app_id and app_code) mcguffin/leaflet-providers
2 participants
@mcguffin @brunob