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
Documentation for building OAuth clients #1784
Comments
This would be very helpful! Thank you in advance :) |
I was just searching something like this, I didn't know even that some CLI command exist yet for OAuth clients registration. I will try with the CLI but would be really helpful to know what's the best approach 👍 |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Since this is now implemented in the Console, here are some starting points for the documentation:
Once the OAuth client registration is approved (or once issue 49 is implemented) you can start using the OAuth client with the following settings:
When working with multi-tenant deployments, things get a bit more complicated, but I think this is a good start. |
Bumping back to triage for re-assignment and planning. cc: @NicolasMrad |
@nejraselimovic can you handle this? |
Not sure if I understand these concepts completely, but if it's not urgent you can assign it to me and I'll do a bit research and look into it. |
This is moved to the docs repo; #1784 |
Summary
It would be good to write some documentation for registering (and working with) OAuth clients.
Why do we need this ?
To help users integrate The Things Stack with their applications.
What is already there? What do you see now?
ttn-lw-cli
commands to manage OAuth clientsWhat is missing? What do you want to see?
Documentation for how to register, what scopes to ask for, maybe an example OAuth flow.
Can you do this yourself and submit a Pull Request?
Yes
The text was updated successfully, but these errors were encountered: