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

readme: clarify usage of the JWT private key #16

Merged
merged 1 commit into from
Dec 11, 2024

Conversation

paulRbr
Copy link
Member

@paulRbr paulRbr commented Dec 11, 2024

Saying that the client is using the private key isn't really
clear. Indeed the private key is not used by the browsers client, but
the server “client”.

I tried to clarify this by modifying the sentence.

Let me know if you have a better phrasing.

Saying that the client is using the private key isn't really
clear. Indeed the private key is not used by the browsers client, but
the server “client”.

I tried to clarify this by modifying the sentence.

Let me know if you have a better phrasing.
@paulRbr paulRbr self-assigned this Dec 11, 2024
@hack3rvaillant
Copy link
Contributor

I think that it depends of the use case. If you have a SPA there it could be only on the client side. CORS proxies are really useful for SPAs.

@paulRbr
Copy link
Member Author

paulRbr commented Dec 11, 2024

I think that it depends of the use case. If you have a SPA there it could be only on the client side. CORS proxies are really useful for SPAs.

What I meant is that you wouldn't want a private key to be included in a web client (be it a SPA or not)

@paulRbr paulRbr merged commit 80c8100 into bump-sh:main Dec 11, 2024
1 check passed
@paulRbr paulRbr deleted the clarify-jwt-private-key-usage branch December 12, 2024 09:10
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

Successfully merging this pull request may close these issues.

2 participants