Custom OAuth config not created even if all env vars are set

[saplla]

Description:

Installing Rocket Chat with a Helm chart, I'm specifying all the required variables to configure a custom OAuth provider as environment variables. E.g. I create env vars called:

  Accounts_OAuth_Custom-Keycloak: true
  Accounts_OAuth_Custom-Keycloak-url: https://example.com/auth
  ...

When I log into the Rocket Chat, no custom OAuth provider called Keycloak has been created. But if I create one called Keycloak, it populates all the fields from the env vars I supplied. This is preventing me automating the deployment of Rocket Chat with Helm.

Server Setup Information:

• Version of Rocket.Chat Server: rocket.chat:0.62.2 (docker hub image)
• Operating System: N/A (kubernetes)
• Deployment Method(snap/docker/tar/etc): helm
• Number of Running Instances: 1
• DB Replicaset Oplog: n/a
• Node Version: unknown
• mongoDB Version: mongodb:0.4.15 (docker hub image)

Steps to Reproduce:

1. Clone https://github.com/kubernetes/charts/tree/master/stable/rocketchat, and add the following to values.yaml:

config:
  Accounts_OAuth_Custom-Keycloak: true
  Accounts_OAuth_Custom-Keycloak-url: https://example.com/my-auth
  Accounts_OAuth_Custom-Keycloak-token_sent_via: Header

2. Install with helm
3. Log in as an admin. Go to Administration -> oauth. No custom provider called Keycloak will exist.
4. Create a custom provider and call it Keycloak. The values will be populated from the above config values.

Expected behavior:

Rocket chat should notice that env vars for the custom provider exist and should create the custom provider automatically.

Actual behavior:

The custom provider needs to be created manually, but then it loads values supplied as env vars.

Relevant logs:

[engelgabriel]

The documentation about Keycloak is going to be written. Please follow https://github.com/RocketChat/docs/issues/790 and fell free to help us :)

[mbrodala]

@engelgabriel While that may work for Keycloak it doesn't solve the specific issue mentioned here. Any other 3rd party OAuth provider cannot be used unless added manually.

[danielmcc123]

+1 for this

[col-panic]

Please see next post - this post is invalid

I assume that using environment variables will not work here.

The default environment variables that are going to be set (like LDAP) are sent to the default settings (see API, but there exists a separate API point for oauth settings.

I fetched my keycloak configuration from this settings.oauth and got

{
    "services": [
        {
            "_id": "JMGe4JFHofdJcYsX4",
            "service": "keycloak",
            "accessTokenParam": "access_token",
            "authorizePath": "/realms/SOME_REALM/protocol/openid-connect/auth",
            "avatarField": "",
            "buttonColor": "#1d74f5",
            "buttonLabelColor": "#FFFFFF",
            "buttonLabelText": "Login with Keycloak",
            "clientId": "rocket-chat-client",
            "custom": true,
            "identityPath": "/realms/SOME_REALM/protocol/openid-connect/userinfo",
            "identityTokenSentVia": "default",
            "loginStyle": "redirect",
            "mergeRoles": true,
            "mergeUsers": false,
            "nameField": "",
            "rolesClaim": "roles",
            "scope": "openid",
            "serverURL": "https://SOME_HOST/keycloak/auth",
            "tokenPath": "/realms/SOME_REALM/protocol/openid-connect/token",
            "tokenSentVia": "header",
            "usernameField": ""
        }
    ],
    "success": true
}

Does anybody know, how to adress these separate settings via the environment variables, and if this is currently supported at all? https://rocket.chat/docs/administrator-guides/settings-via-env-vars/ does not show any respective information.

[col-panic]

My post was not addressing the real problem here - which I could re-enact with 2.0.0 and also have to manually add a custom oauth method.

[col-panic]

@engelgabriel could you please have a look at this?