Open TheRealGramdalf opened 3 months ago
Hello, @TheRealGramdalf. Can you share more about your use/business case for it? Having a single IdP is the case for most organizations.
In my particular case it was more about using a client ID of my choice, rather than being forced to use netbird
. I haven't (yet) had the need to actually add multiple netbird servers, but it's also a limitation which might come back to bite you later.
Is your feature request related to a problem? Please describe.
The mobile app currently uses a hard coded client ID (
netbird
). This means that there is a limit of one netbird server per IDP, as there can only be one client ID callednetbird
per instance.Describe the solution you'd like Rather than hardcoding the client ID into the app, it should be dynamically queried from the netbird management server you connect to. This allows freedom in that of the client ID without requiring a custom build of the client application.
Describe alternatives you've considered Leave the client ID hardcoded, as situations with multiple netbird management servers might be rare.
Additional context My IDP of choice is Kanidm, though I believe this applies to the majority of IDPs out there.