-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement new OAuth flow #241
Comments
Would it still be possible to add a simple api token if this is implemented? We have to get sure that this can also be provisioned on many devices without user interaction via predefined config file on SD card |
It doesn't matter where the refresh-token comes from. It will end up in config, so you can feed it through the login "wizard" in the browser or sideload it through config on SD. But you shouldn't. Each device should have its own token, so you can invalidate them independently. If you're logged in to the portal on the device you use for configuration, then logging in the device is a one or two click process. Probably easier even than finding the refresh token and moving it to some config file in the right format. We also have |
Starting v0.2, the Portal will have a proper OAuth Authorization Code flow implemented and we can use that in the configserver to connect a user account. It allows us to have a simple "Log in with OpenBikeSensor Portal" button instead of having to copy-paste API Keys.
This is a bit of code, and can be implemented in 95% JavaScript for developer convenience. It will require:
This does not yet work on the currently deployed HLRS instance, but that one is deprecated anyway. We can already start writing this component and release it when we have the new portal up and running.
The text was updated successfully, but these errors were encountered: