Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
steering
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
AURA
steering
Commits
a238920f
Commit
a238920f
authored
3 years ago
by
jackie / Andrea Ida Malkah Klaura
Browse files
Options
Downloads
Patches
Plain Diff
add section on OIDC client setup to README
parent
b4e7a088
No related branches found
No related tags found
1 merge request
!13
Adaptation for an AuRa wide docker setup
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.rst
+22
-0
22 additions, 0 deletions
README.rst
with
22 additions
and
0 deletions
README.rst
+
22
−
0
View file @
a238920f
...
@@ -92,3 +92,25 @@ with the credentials you have chosen in the ``createsuperuser`` command.
...
@@ -92,3 +92,25 @@ with the credentials you have chosen in the ``createsuperuser`` command.
If you are using some placeholder credentials, make sure to change your password
If you are using some placeholder credentials, make sure to change your password
by visiting http://127.0.0.1:8000/admin/auth/user/1/password/
by visiting http://127.0.0.1:8000/admin/auth/user/1/password/
Configuring OpenID Connect clients
----------------------------------
To make AuRa usable, you have to set up OpenID Connect (OIDC) clients for the
*dashboard* and *tank*, so they can make authenticated requests on behalf of
the user against the *steering* API.
To do so, you can either visit the Django admin interface and create an RSA key
as well as two clients, or do so programmatically by running::
(python)$ python manage.py creatersakey
(python)$ python manage.py create_oidc_client dashboard public -r "id_token token" -u https://aura-test.o94.at/oidc_callback.html -u https://aura-test.o94.at/oidc_callback_silentRenew.html -p https://aura-test.o94.at/
(python)$ python manage.py create_oidc_client tank confidential -r "code" -u https://aura-test.o94.at/tank/auth/oidc/callback
In these examples you will have to *https://aura-test.o94.at* and
*https://aura-test.o94.at/tank_with* with wherever *dashboard* and *tank* are
running in your setup. In a local development environment this might be
something like *http://localhost:8080* and *http://localhost:4000* respectively.
The client id and in case of the tank also the client secret are then needed for
the configuration of those components.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment