AURA Steering is the scheduling module, where the actual program schedule of
the whole station is stored as well as all infos regarding single shows and
AURA Steering is the scheduling module, where the actual program schedule of the
whole station is stored as well as all infos regarding single shows and
emissions.
It also acts as an OpenID Connect provider for `dashboard` and `tank`.
...
...
@@ -29,23 +29,26 @@ And load the fixtures::
$ docker compose run django ./manage.py loaddata fixtures/*/*.json
Or, if you prefer, you can just create a super user after setting up the database::
Or, if you prefer, you can just create a super user after setting up the
database::
$ docker compose run django python manage.py createsuperuser
Then, you can create a RSA Key and the clients for `dashboard` and `tank`::
$ docker compose run django ./manage.py creatersakey
$ docker compose run django ./manage.py create_oidc_client dashboard public -r "id_token token" -u https://localhost:8080/oidc_callback.html -u https://localhost:8080/oidc_callback_silentRenew.html -p https://localhost:8080/
$ docker compose run django ./manage.py create_oidc_client tank confidential -r "code" -u https://localhost:8040/auth/oidc/callback
$ docker compose run django ./manage.py create_oidc_client dashboard public -r "id_token token" -u http://localhost:8080/oidc_callback.html -u http://localhost:8080/oidc_callback_silentRenew.html -p http://localhost:8080/
$ docker compose run django ./manage.py create_oidc_client tank confidential -r "code" -u http://localhost:8040/auth/oidc/callback
If you prefer to use the admin interface for this, refer to the [OpenID ClientConfiguration](https://gitlab.servus.at/aura/meta/-/blob/master/docs/administration/oidc-client-config.md#registering-oidc-clients-via-the-admin-interface).
If you prefer to use the admin interface for this, refer to the [OpenID Client
