You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After discussing with the team, I received advice for a better approach than having users issue JWTs themselves.
Instead of users manually generating tokens, I will follow the standard structure where a JWT server issues tokens. However, the process for obtaining the token (similar to the login process in traditional web services) will involve users signing a specific random value with their private key and sending it.
This approach simplifies the process for users by eliminating the need to handle token issuance, expiration, and service-specific details themselves, making it as seamless as a typical web login.
After discussing with the team, I received advice for a better approach than having users issue JWTs themselves.
Instead of users manually generating tokens, I will follow the standard structure where a JWT server issues tokens. However, the process for obtaining the token (similar to the login process in traditional web services) will involve users signing a specific random value with their private key and sending it.
This approach simplifies the process for users by eliminating the need to handle token issuance, expiration, and service-specific details themselves, making it as seamless as a typical web login.
Originally posted by @Atralupus in #33 (comment)
The text was updated successfully, but these errors were encountered: