DigitalOcean token management change
-
I just saw that DigitalOcean is changing its API token management. Is this something we have to act on if we use DigitalOcean API access for Cloudron?
-
I think nothing needs to be done. But they encourage you to go ahead and create a new token because new ones have extra feature like token expiry (and maybe even scopes).
It just says "We encourage you to revoke any old tokens no longer in use and re-generate your existing tokens at your earliest convenience."
-
I think nothing needs to be done. But they encourage you to go ahead and create a new token because new ones have extra feature like token expiry (and maybe even scopes).
It just says "We encourage you to revoke any old tokens no longer in use and re-generate your existing tokens at your earliest convenience."
-
-
@nebulon ah ok. is that information somewhere in that post? I re-read and can't see it in that post.
-
Any further thoughts on this? It isn't clear to me when the cutoff is for tokens being old. But my main Cloudron token is 4 years old. If I regenerate it in DigitalOcean, what do I do to update it on Cloudron? Just in Domains and Certs, or somewhere else?
-
Any further thoughts on this? It isn't clear to me when the cutoff is for tokens being old. But my main Cloudron token is 4 years old. If I regenerate it in DigitalOcean, what do I do to update it on Cloudron? Just in Domains and Certs, or somewhere else?
@ntnsndr yes, just in the domains view.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better đź’—
Register Login