Description
Hi all, Microsoft OAuth provider settings are not correctly added to secret when deploying Hoppscotch using current Helm chart.
The following message is observed in POD logs:
Backend Server | MICROSOFT SSO auth provider(s) are not configured properly in .env file. Do configure them from Admin Dashboard.
when using the following configuration for OAuth in custom_values.yaml file:
community:
config:
auth:
microsoft:
clientId: REDACTED_CLIENTID
clientSecret: REDACTED_CLIENTSECRET
callbackUrl: https://FQDN/v1/auth/microsoft/callback
scope: user.read
tenant: REDACTED_TENANT
Values corresponding to callbackUrl, scope and tenant are missing in the the secret after deployment of the application, leading to error message present in log and the inability to use microsoft authentication provider.
According to the template currently defined for the secret, the only lines present are:
MICROSOFT_CLIENT_ID: {{ .Values.community.config.auth.microsoft.clientId | b64enc }}
MICROSOFT_CLIENT_SECRET: {{ .Values.community.config.auth.microsoft.clientSecret | b64enc }}
It would be necessary to add the following lines:
MICROSOFT_SCOPE: {{ .Values.community.config.auth.microsoft.scope | b64enc }}
MICROSOFT_TENANT: {{ .Values.community.config.auth.microsoft.tenant | b64enc }}
MICROSOFT_CALLBACK_URL: {{ .Values.community.config.auth.microsoft.callbackUrl | b64enc }}
This ensures the configuration is complete and MS can be used as an authentication provider correctly.
Regards.