Releases #11
CLI OAuth 2.0 authentication and data security improvements 🔐 CLI OAuth 2.0 authentication Now you can authenticate in the Runops CLI using Google, Github, or a custom username + password of your choice. This is an improvement over the previous key-based authentication. Now we only store Bearer tokens locally. Tokens expire and get renewed often. You can now use additional authentication factors trough Google and Github integratinos. ␖ Data security improvements We removed all potentially
this topic: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
CLI OAuth 2.0 authentication and data security improvements
🔐 CLI OAuth 2.0 authentication
Now you can authenticate in the Runops CLI using Google, Github, or a custom username + password of your choice. This is an improvement over the previous key-based authentication. Now we only store Bearer tokens locally. Tokens expire and get renewed often. You can now use additional authentication factors trough Google and Github integratinos.
␖ Data security improvements
We removed all potentially sensitive data access by Runops. The logs from your tasks now get PII redacted before they touch any storage mechanism. Now besides not storing or having access to your secrets, we apply the same principles to your data.