Expose dex's connectors in combined server configuration

[adamcstephens]

Before posting

• I searched existing discussions and issues for similar requests.
• I checked the documentation to confirm this is not already supported.
• This is a product idea or enhancement request, not a support question.
• I removed or anonymized sensitive details from examples and screenshots.

Product area

Management service / API, Identity provider / SSO, Self-hosting / Deployment

Problem or use case

As a server admin I want to configure OIDC statically on initial provision.

Proposed solution

The management server configuration already supports staticConnectors = [] for creating these. I propose to expose this same capability through the combined server.

I've tested that this works with:

diff --git i/combined/cmd/config.go w/combined/cmd/config.go
index 890c86876..736ab6cd6 100644
--- i/combined/cmd/config.go
+++ w/combined/cmd/config.go
@@ -13,6 +13,7 @@ import (
 	log "github.com/sirupsen/logrus"
 	"gopkg.in/yaml.v3"
 
+	"github.com/netbirdio/netbird/idp/dex"
 	"github.com/netbirdio/netbird/management/server/idp"
 	"github.com/netbirdio/netbird/management/server/types"
 	"github.com/netbirdio/netbird/util"
@@ -155,6 +156,7 @@ type AuthConfig struct {
 	Owner                           *AuthOwnerConfig  `yaml:"owner,omitempty"`
 	DashboardPostLogoutRedirectURIs []string          `yaml:"dashboardPostLogoutRedirectURIs"`
 	GrantTypes                      []string          `yaml:"grantTypes"`
+	StaticConnectors                []dex.Connector   `yaml:"staticConnectors"`
 }
 
 // AuthStorageConfig contains auth storage settings
@@ -628,6 +630,7 @@ func (c *CombinedConfig) buildEmbeddedIdPConfig(mgmt ManagementConfig) (*idp.Emb
 		CLIRedirectURIs:                 mgmt.Auth.CLIRedirectURIs,
 		DashboardPostLogoutRedirectURIs: mgmt.Auth.DashboardPostLogoutRedirectURIs,
 		GrantTypes:                      mgmt.Auth.GrantTypes,
+		StaticConnectors:                mgmt.Auth.StaticConnectors,
 	}
 
 	if mgmt.Auth.Owner != nil && mgmt.Auth.Owner.Email != "" {

Alternatives or workarounds considered

No response

Community impact and priority

• unknown number of users
• self-hosted deployment admins with oidc

Examples from other tools or products

No response

Security, privacy, and compatibility considerations

No response

Implementation ideas

No response

Are you willing to help?

Yes, I can submit a PR if the approach is accepted.

Additional context

No response