-
Notifications
You must be signed in to change notification settings - Fork 56
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
Stop using CryptoJS for signing token requests #1295
Comments
➤ Automation for Jira commented: The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3605 |
lawrence-forooghian
added a commit
that referenced
this issue
Jun 1, 2023
TODO implement this Resolves #1295.
This was referenced Jun 1, 2023
lawrence-forooghian
added a commit
that referenced
this issue
Jun 6, 2023
TODO implement this TODO figure out secure context stuff Resolves #1295.
lawrence-forooghian
added a commit
that referenced
this issue
Jun 6, 2023
TODO figure out secure context stuff Resolves #1295.
lawrence-forooghian
added a commit
that referenced
this issue
Jun 6, 2023
TODO figure out secure context stuff Resolves #1295.
lawrence-forooghian
added a commit
that referenced
this issue
Jun 6, 2023
TODO figure out secure context stuff and what the broad-reaching implications are Resolves #1295. TODO what can we use as the statusCode and code — used generic "bad request"
lawrence-forooghian
added a commit
that referenced
this issue
Jun 6, 2023
TODO figure out secure context stuff and what the broad-reaching implications are Resolves #1295. TODO what can we use as the statusCode and code — used generic "bad request"
Closed by #1325. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Split from #1239.
Replace the web token signing code’s use of
crypto-js
with the Web Crypto API (or something else that doesn't increase bundle size much, if we decide we want to access HMAC in non-secure contexts).The text was updated successfully, but these errors were encountered: