Misha Bragin

> Oh, you have a bff, then you should offer authorization code flow with a confidential client + PKCE. > > I am not so much "concerned" about the validation...

Hey guys, We came across Zitadel -> https://github.com/zitadel/zitadel It looks like an excellent option for us, except that they don't yet support a device flow that we need for our...

Hey guys, just letting you know that we have started working on the generic OIDC support. Most of the work has been done by @mlsmaycon and there are some bugs...

Hey everyone! I brought some good news :) We have just merged #60, thanks to @mlsmaycon! We introduced a generic OIDC library within this PR and achieved compatibility with Auth0....

FYI: I'm working on some generic OIDC adjustments here https://github.com/netbirdio/dashboard/pull/66 Just tested Keycloak :)

Hey everyone. The Keycloak integration guide is there, check it out! https://netbird.io/docs/integrations/identity-providers/self-hosted/using-netbird-with-keycloak

Hey @ykorzikowski Are you running Dashboard and API on different machines, right? It might be that for the gRPC API a default 33073 port is used, as per the docker-compose.yml...

We didn't try it yet with Ngnix but there should be some config that allows gRPC connections. The Management service exposes gRPC API to clients to fetch the network config....

> So the netbird client uses the gRPC-API and not HTTP? Yes, exactly. The HTTP API is used by the Dashboard. We will be putting things behind Caddy for simpler...

I see, I think this one will be easy to fix. The Keycloak is fine. How did you start the client? This way? ``` netbird up --management-url https://netbird-api.company.com/ ``` You...