Skip to content

API key has an expiration date in the future #55

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.

Sign up for GitHub

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

Open
kristianrl wants to merge 1 commit into
base: master
Choose a base branch
from
Open

API key has an expiration date in the future #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions source/internal-interface-design/api-key-access.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ What you can access and manage is limited by the user group (-s) tied to the API
With that in mind, let's dive into using an API key. Let's make a few assumptions:

- We have an API key with the value :code:`00000000-abcd-ef00-0000-012345678901`
- The API key has an expiration date in the future
- This API key is tied to a user group with Read priviliges to an organization and all its applications
- There exists a :code:`GET` endpoint for fetching applications. The route ends with :code:`/application`
- The Base URL for the OS2IOT Backend is known, e.g. :code:`https://os2iot-backend.SERVERNAME.EXAMPLE/api/v1/chirpstack/`
Expand Down