Request for OIDC Integration Examples - Connecting Planka, Vikunja, and Grist

[Ryanmwangi]

Hello,
First off, thank you for creating and maintaining Rauthy - it's an excellent privacy-focused IAM solution that aligns perfectly with our project goals.

Context
We're building a new open-source workspace solution to replace Google Workspace, focusing on privacy and self-hosting. We've chosen Rauthy as our identity and access management layer, and we're currently working on integrating various collaboration tools.

Request
We're looking to connect the following applications to Rauthy via OIDC:

Planka (project management)
Vikunja (task management)
Grist (spreadsheets/database)
While we understand the OIDC basics, we'd greatly appreciate:

Example configurations of applications you've successfully connected to Rauthy (if available)
Common pitfalls or gotchas when configuring OIDC clients
Best practices for scope and claim mapping
Any documentation or guides you might have for integrating specific applications
Even partial examples or links to existing configurations would be incredibly helpful for us and likely beneficial for the broader community.

Our Setup
We're running Rauthy v0.32.5 behind Traefik as a reverse proxy with Let's Encrypt SSL. Happy to share more details about our configuration if that helps.

Thanks again for your work on this project, supporting privacy-focused alternatives to big tech is important work!

[sebadob]

There is really not that much to it. OIDC is pretty simple and straightforward.

Common pitfalls or gotchas when configuring OIDC clients

Rauthy protects you from these and doesn't even allow them.

Best practices for scope and claim mapping

Only request the data you actually need, that's it.

Any documentation or guides you might have for integrating specific applications

I have integrated many applications, but no specific example code. With OIDC, it's always the same procedure and not much to configure. Most values can even be auto-configured via the openid-configuration endpoint, and simply be copy & pasted from there if not. Apart from that, you only need to specify the scope you need for your application and copy & paste client_id and secret. In 99% of cases, you will use the authorization_code flow and if you need anything else, you will know it. The only "important" thing is that you need to figure out the callback URI on your client and configure / allow this on Rauthys side.