-
Notifications
You must be signed in to change notification settings - Fork 462
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
Twilio::JWT::AccessToken not working for API KEYS outside US1 #628
Comments
Hi @ppascualv, Thank you for posting this, we are currently looking into this issue. |
Hey @ppascualv, I am not able to reproduce this issue. Can you please provide more insights into what you are trying to achieve? (debugging information or full code) This is what I have tested: Note: you have to specify the edge as well while initialising the client.
|
The JWT is correctly generated but when you try to call using this JWT with a frontend app, the JWT is not working properly. Does the javascript client have a different configuration in order to use the Dublin edge? |
For setting an edge location for javascript client, refer this. |
Still not working, the token is generated but the call is not working |
Can you please share the code you have written to make the call, and the associated error logs ? |
I'm getting this error
I'm doing the call from the frontend
|
Are you still facing problem with the JWT token based on region? |
Issue Summary
Twilio::JWT::AccessToken only works when api keys are generated on US1 region.
Steps to Reproduce
Code Snippet
Exception/Log
Technical details:
The text was updated successfully, but these errors were encountered: