-
Notifications
You must be signed in to change notification settings - Fork 4
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
feat: basic jwt support #17
Conversation
@@ -18,13 +20,15 @@ class Saturn { | |||
clientId: randomUUID(), | |||
cdnURL: 'saturn.ms', | |||
logURL: 'https://twb3qukm2i654i3tnvx36char40aymqq.lambda-url.us-west-2.on.aws/', | |||
authURL: 'https://fz3dyeyxmebszwhuiky7vggmsu0rlkoy.lambda-url.us-west-2.on.aws/', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the staging lambda url, will switch with prod when we upgrade
1bdd38f
to
a2e8ce7
Compare
tests failing due to new clientKey requirement.. just add random clientKey to our test clients? |
I just realized that test clients perform fetches, so the JWT fetching logic will be called as well.., requiring a real clientKey for the target environment. How should we proceed? Do we mock out the authURL or somethin |
No description provided.