local-it/mitgliederverwaltung
2
3
Fork 0
Code Issues 51 Pull requests 14 Projects 1 Releases Packages 1 Activity Actions

Add docs for testing SSO #101

Merged
carla merged 3 commits from push-okkoxvykzxmz into main 2025-08-14 16:57:26 +02:00
Conversation 4 Commits 3 Files changed 2 +17
2 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
.env.example Normal file
View file

@ -0,0 +1 @@
OIDC_CLIENT_SECRET=

16
README.md
View file

@ -1,2 +1,18 @@
# mitgliederverwaltung
## Testing SSO with rauthy
1. `just run`
1. go to [localhost:8080](http://localhost:8080), go to the Admin area
1. Login with "admin@localhost" and password from `BOOTSTRAP_ADMIN_PASSWORD_PLAIN` in docker-compose.yml
carla marked this conversation as resolved Outdated
moritz commented 2025-07-17 20:08:28 +02:00
Outdated
Copy link

There is no dev/rauthy/config.toml for me. I can find the password in the logs: docker logs rauthy-dev. Unfortunately the docker-compose env BOOTSTRAP_ADMIN_PASSWORD_PLAIN does not work for me.

There is no `dev/rauthy/config.toml` for me. I can find the password in the logs: `docker logs rauthy-dev`. Unfortunately the docker-compose env `BOOTSTRAP_ADMIN_PASSWORD_PLAIN` does not work for me.
carla commented 2025-07-21 10:51:13 +02:00
Outdated
Copy link

Somehow this stopped working, even if it is exactly as described in the docs.
We can either create an issue to check bootstrapping again or we describe the way to 1. get the password from the logs and then 2. reset the password with a comfortable one accessing the reset mail. What do you think?

Somehow this stopped working, even if it is exactly as described in the docs. We can either create an issue to check bootstrapping again or we describe the way to 1. get the password from the logs and then 2. reset the password with a comfortable one accessing the reset mail. What do you think?
moritz commented 2025-07-21 12:51:09 +02:00
Outdated
Copy link

I would favor to check the bootstrapping again. Setting a fixed password in the env would make the dev setup easier.

I would favor to check the bootstrapping again. Setting a fixed password in the env would make the dev setup easier.
👍 1
carla commented 2025-07-21 15:10:28 +02:00
Outdated
Copy link

#113

https://git.local-it.org/local-it/mitgliederverwaltung/issues/113
1. add client from the admin panel
- Client ID: mv
- redirect uris: http://localhost:4000/auth/user/rauthy/callback
- Authorization Flows: authorization_code
- allowed origins: http://localhost:4000
- access/id token algortihm: RS256 (EDDSA did not work for me, found just few infos in the ashauthentication docs)
1. copy client secret to `.env` file
1. abort and run `just run` again