The Clusternator currently supports two two authentication mechanisms:
- bearer tokens
The Clusternator supports passwords. Passwords are used (transparently to the user) to acquire bearer tokens.
In real world practice, Clusternator users would
Upon success, The Clusternator would locally save a bearer token. Then use it to execute subsequent commands.
Users can change their password with:
The Clusternator uses a library called Passport and can be extended. Using GitHub to authenticate is something we’re really hoping to have the time to implement soon.