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
While I'm really enjoying CryoSPARC tools, I think it could benefit from token-based auth for two majors reasons:
So that users aren't tempted to leave their password in plain text in Python files everywhere.
In a commercial setting, people may not want the license key hanging around in text files everywhere (or even have access to the license key).
Some sort of revokable authentication token that each user can generate in their CryoSPARC instance would really help make cryosparc-tools more usable. Users could then just submit the URL, port, and auth token. It could be a per-use token, or a long-lived one that simply is able to be revoked, or expire after some period of time.
The text was updated successfully, but these errors were encountered:
ccgauvin94
changed the title
Token-based authentication
Request: Token-based authentication
Nov 28, 2023
I absolutely agree with you that this would be extremely helpful!
I'll add my situation as an example.
I manage several lab wide CryoSPARC instances and when a new person joins a lab I create them an account on the appropriate CryoSPARC instance and send them their token and instructions on how to access their lab's CryoSPARC instance. The user's never know what the CryoSPARC license is for their instance and I do not want the license keys sitting in a text or python file somewhere.
While I'm really enjoying CryoSPARC tools, I think it could benefit from token-based auth for two majors reasons:
Some sort of revokable authentication token that each user can generate in their CryoSPARC instance would really help make cryosparc-tools more usable. Users could then just submit the URL, port, and auth token. It could be a per-use token, or a long-lived one that simply is able to be revoked, or expire after some period of time.
The text was updated successfully, but these errors were encountered: