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.

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

Replacing API keys with Access Tokens #45

Closed
Svrkota-S opened this issue Apr 18, 2018 · 1 comment
Closed

Replacing API keys with Access Tokens #45

Svrkota-S opened this issue Apr 18, 2018 · 1 comment

Comments

@Svrkota-S
Copy link

Svrkota-S commented Apr 18, 2018

Hi, is ng-intercom going to publish an update in order to support latest update with Access Tokens? You can read about it here: https://developers.intercom.com/v2.0/docs/replacing-your-api-keys-with-access-tokens-step-by-step-guide#section-step-2-replace-your-api-keys

I received an email which says:

As you may be aware, we've been in the process of deprecating API Keys over the past 18 months in favour of more secure methods. As the final step of this process, your API Keys will be disabled at 4pm GMT on April 23 2018.

Thanks in advance for any reply!

@scott-wyatt
Copy link
Member

Hi! We actually use the appId in ng-intercom, we don't use the api key at all. With a client side application, you really don't want to expose your key or token, which is why intercom allows for the appId to drive the client side communication. Hope this helps, cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants