Skip to content

Microsoft OAuth provider settings missing in secret #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RealObjetor opened this issue May 19, 2025 · 0 comments
Open

Microsoft OAuth provider settings missing in secret #19

RealObjetor opened this issue May 19, 2025 · 0 comments

Comments

@RealObjetor
Copy link

RealObjetor commented May 19, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant