Google Workspace SCIM problem

[aspantel]

After clicking Google Workspace Connect I get:
{"error":"bad_request","message":"unsupported provider: "GOOGLE_WORKSPACE""}

[gearnode]

Hi @aspantel, thanks for reporting this.

This error (unsupported provider: "GOOGLE_WORKSPACE") is returned when the GOOGLE_WORKSPACE connector isn't registered in your Probo configuration. The connector registry is built from the connectors: section of your config file, and any provider missing from that list is rejected as unsupported.

To fix it, add a GOOGLE_WORKSPACE entry to the connectors: block of your config file, for example:

connectors:
  - provider: "GOOGLE_WORKSPACE"
    protocol: "oauth2"
    config:
      client-id: "your-google-client-id.apps.googleusercontent.com"
      client-secret: "your-google-client-secret"

You'll need a Google Cloud OAuth 2.0 client. The redirect URI to register on Google's side is <your-probo-console-url>/api/console/v1/connectors/callback.

A full example is available in cfg/dev.yaml in the repo.

Once added, restart probod and the Connect button should work. Let me know if that resolves it.

[aspantel]

We use Docker and ENV variables. are there variables for this provider? Thank you

[gearnode]

Not yet. We'll add support for configuring connectors via environment variables shortly. For now the connectors: section of the YAML config is the only way.

[aspantel]

is this for OpenId login into probo, instead of SSO?

Google: probod.OIDCProviderConfig{
ClientID: b.getEnv("AUTH_GOOGLE_CLIENT_ID"),
ClientSecret: b.getEnv("AUTH_GOOGLE_CLIENT_SECRET"),
Enabled: b.getEnv("AUTH_GOOGLE_CLIENT_ID") != "" && b.getEnv("AUTH_GOOGLE_CLIENT_SECRET") != "",
},

[aspantel]

Sounds like I need to mount a volume with the config file, right?
When do you think you'll add the ENV support?