Component - Add custom Zitadel IDP component to aspire

[MadL1me]

.NET Aspire issue link

dotnet/aspire#6988

Overview

While the keycloak is widely used, there is some issues with it, especially in high load situations. There are a lot of different IDPs (Identitiy Providers), which can be used, with SDKs in dotnet as well (Auth0, LogTo, Authentic, etc)

The issues proposes adding component for one of the promising IDP, our company and many others using - Zitadel.

Usage example

Same as any other component

Additional context

No response

Help us help you

Yes, I'd like to be assigned to work on this item

[github-actions]

We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use /stale-extend to extend the window.

[Foxtrek64]

I am definitely keeping an eye on this issue. I made my own Aspire-Zitadel integration earlier but it would be nice to adopt a library with broader visibility and support rather than something homebrew.

[aaronpowell]

I am definitely keeping an eye on this issue. I made my own Aspire-Zitadel integration earlier but it would be nice to adopt a library with broader visibility and support rather than something homebrew.

Happy for you to contribute it here if you would like

[Foxtrek64]

I am definitely keeping an eye on this issue. I made my own Aspire-Zitadel integration earlier but it would be nice to adopt a library with broader visibility and support rather than something homebrew.

Happy for you to contribute it here if you would like

I should be able to get a PR in here soon, worst case by this weekend. Do I need to make a proposal champion first? Didn't see it in the contribution guide but it's possible I just missed it.

[aaronpowell]

No, linking to this issue is fine. Also, happy for you to join as a contributor and be the CODEOWNER of the integration

[github-actions]

We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use /stale-extend to extend the window.

[Foxtrek64]

Sorry, a bit behind on this! It's crunch time for several projects so I've not been able to allocate time to this. Just wanted to leave a note that this has not been forgotten.

I should have time either tomorrow or this weekend to get that PR in.

[aaronpowell]

/stale-extend

[aaronpowell]

No stress @Foxtrek64 - our stale issue monitor is more to ensure we don't have a massive backlog of stuff that never gets actioned.

[Foxtrek64]

PR #549 has been submitted, albeit currently as WIP. I lost my original code (doesn't seem to be anywhere in git and I'm usually pretty good about checking in code), so I've needed to recreate it from scratch. This is where the additional time to implement has come from.

The WIP PR is about 90% done - just need to add in database support, the health check, and get documentation and tests written. Otherwise we're just about good to go.