local OIDC provider for testing

[fabis94]

Should work automatically for new local instances, but existing ones (w/ existing DB) will need to run the SQL init file manually before starting up keycloak.

LOCAL SETUP

1. For existing docker compose deployments, invoke SQL found in setup/db/11-docker_postgres_keycloack_init.sql in your DB client manually (as the speckle user). New docker compose deployments can skip this step.
2. yarn dev:docker:up
3. Copy OIDC strategy env vars from .env-example into .env (in server)
4. When logging in in FE2, use speckle:speckle or register a new keycloak account

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[iainsproat]

@fabis94

• this duplicates @alemagio PR, I think Alessandro/keycloak docker compose #2598
• can we add the SQL for Keycloak to the volume mounts for Postgres (line 16 in docker-compose-deps.yml)?

[fabis94]

@iainsproat Alessandro's PR is incomplete, this does the full setup

And I just fixed the 2nd point (altho I think these scripts only run on DB init, so all of us still need to run it manually)

[iainsproat]

@fabis94 - does this PR cover the Identity Provider part of the problem? #2598 (comment)

[fabis94]

@alemagio I didn't have to do any identity provider stuff, I just created a new realm w/ default clients, adjusted some client settings and created a couple of test users. Then I exported that realm and made sure its imported on keycloak init.

I was able to both register and log into Speckle with that, without having to mess around with any identity providers