starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #3679] [bug]: Cannot Update Authentication Providers #1268

New issue

Closed

opened 2026-03-16 19:32:58 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 19:32:58 +03:00

Owner

Originally created by @sats268842 on GitHub (Dec 19, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3679

Is there an existing issue for this?

I have searched the existing issues

Current behavior

I am experiencing an issue when attempting to update the Authentication Providers(Microsoft).

App Version: v2023.12.0-1

{
    "errors": [
        {
            "message": "infra_config/service_not_configured",
            "locations": [
                {
                    "line": 2,
                    "column": 3
                }
            ],
            "path": [
                "enableAndDisableSSO"
            ],
            "extensions": {
                "code": "INTERNAL_SERVER_ERROR",
                "stacktrace": [
                    "Error: infra_config/service_not_configured",
                    "    at throwErr (/usr/src/app/packages/hoppscotch-backend/dist/utils.js:14:11)",
                    "    at InfraConfigService.enableAndDisableSSO (/usr/src/app/packages/hoppscotch-backend/dist/infra-config/infra-config.service.js:167:42)",
                    "    at InfraResolver.enableAndDisableSSO (/usr/src/app/packages/hoppscotch-backend/dist/admin/infra.resolver.js:131:57)",
                    "    at /usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/helpers/external-context-creator.js:67:33",
                    "    at async target (/usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/helpers/external-context-creator.js:74:28)",
                    "    at async Object.enableAndDisableSSO (/usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/helpers/external-proxy.js:9:24)"
                ]
            }
        }
    ],
    "data": null
}

Steps to reproduce

Go to Admin Website
Click on Setting page
Update the authentication providers with Microsoft cred
try to save

Environment

Production

Version

Self-hosted

Originally created by @sats268842 on GitHub (Dec 19, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3679 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior I am experiencing an issue when attempting to update the Authentication Providers(Microsoft). App Version: v2023.12.0-1 ``` { "errors": [ { "message": "infra_config/service_not_configured", "locations": [ { "line": 2, "column": 3 } ], "path": [ "enableAndDisableSSO" ], "extensions": { "code": "INTERNAL_SERVER_ERROR", "stacktrace": [ "Error: infra_config/service_not_configured", " at throwErr (/usr/src/app/packages/hoppscotch-backend/dist/utils.js:14:11)", " at InfraConfigService.enableAndDisableSSO (/usr/src/app/packages/hoppscotch-backend/dist/infra-config/infra-config.service.js:167:42)", " at InfraResolver.enableAndDisableSSO (/usr/src/app/packages/hoppscotch-backend/dist/admin/infra.resolver.js:131:57)", " at /usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/helpers/external-context-creator.js:67:33", " at async target (/usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/helpers/external-context-creator.js:74:28)", " at async Object.enableAndDisableSSO (/usr/src/app/node_modules/.pnpm/@nestjs+core@10.2.7_@nestjs+common@10.2.7_@nestjs+platform-express@10.2.7_reflect-metadata@0.1.13_rxjs@7.6.0/node_modules/@nestjs/core/helpers/external-proxy.js:9:24)" ] } } ], "data": null } ``` ### Steps to reproduce 1. Go to Admin Website 2. Click on Setting page 3. Update the authentication providers with Microsoft cred 4. try to save ### Environment Production ### Version Self-hosted

kerem

2026-03-16 19:32:58 +03:00

closed this issue
added the
bug

need testing

self-host
labels

kerem commented

2026-03-16 19:33:14 +03:00

Author

Owner

@balub commented on GitHub (Dec 22, 2023):

@sats268842 Can I take a look at your .env file, there is a known issue we are working on right now related to auth providers and their callback URLs. Since you mentioned you use microsoft, may I suggest you add the following 2 variables into the .env file and restart the server?

MICROSOFT_CALLBACK_URL
MICROSOFT_SCOPE
MICROSOFT_TENANT

@balub commented on GitHub (Dec 22, 2023): @sats268842 Can I take a look at your `.env` file, there is a known issue we are working on right now related to auth providers and their callback URLs. Since you mentioned you use microsoft, may I suggest you add the following 2 variables into the `.env` file and restart the server? * `MICROSOFT_CALLBACK_URL` * `MICROSOFT_SCOPE` * `MICROSOFT_TENANT`

kerem commented

2026-03-16 19:33:19 +03:00

Author

Owner

@sats268842 commented on GitHub (Dec 22, 2023):

# Microsoft Auth Config
MICROSOFT_CALLBACK_URL=*****/v1/auth/microsoft/callback
MICROSOFT_SCOPE=user.read
MICROSOFT_TENANT=common
MICROSOFT_CLIENT_SECRET=********
MICROSOFT_CLIENT_ID=*********

Current Configuration in .env file @balub

@sats268842 commented on GitHub (Dec 22, 2023): ``` # Microsoft Auth Config MICROSOFT_CALLBACK_URL=*****/v1/auth/microsoft/callback MICROSOFT_SCOPE=user.read MICROSOFT_TENANT=common MICROSOFT_CLIENT_SECRET=******** MICROSOFT_CLIENT_ID=********* ``` Current Configuration in .env file @balub

kerem commented

2026-03-16 19:33:24 +03:00

Author

Owner

@balub commented on GitHub (Dec 22, 2023):

@sats268842 We will have a point release coming soon that will hopefully fix this issue. Also another question I have did you try disabling all auth providers when you encountered this issue?

@balub commented on GitHub (Dec 22, 2023): @sats268842 We will have a point release coming soon that will hopefully fix this issue. Also another question I have did you try disabling all auth providers when you encountered this issue?

kerem commented

2026-03-16 19:33:29 +03:00

Author

Owner

@sats268842 commented on GitHub (Dec 22, 2023):

@balub I can disable the auth provider, but I can't enable it again, so I have to reset configuration from the UI.

@sats268842 commented on GitHub (Dec 22, 2023): @balub I can disable the auth provider, but I can't enable it again, so I have to reset configuration from the UI.

kerem referenced this issue

2026-03-17 00:49:31 +03:00

[PR #1268] [MERGED] Update french language #3189

kerem referenced this issue

2026-03-17 00:49:48 +03:00

[PR #1277] [MERGED] i18n #3192