mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 17:26:03 +03:00
[GH-ISSUE #3483] [bug]: Auth providers show although they are deactivated #1179
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1179
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Breee on GitHub (Oct 31, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3483
Is there an existing issue for this?
Current behavior
Our current setup is:
we have set:
In the admin frontend this works as expected:
In the frontend not:
Steps to reproduce
Full config example:
Environment
Production
Version
Self-hosted
@Ev3rdown commented on GitHub (Nov 7, 2023):
Are you sure you it's not the frontend cache ?
You can test with an other browser/in private just to be sure.
The cache is stupidly difficult to clear, even the updates don't clear it, so if you tried using hoppscotch even only once with a different VITE_ALLOWED_AUTH_PROVIDERS, it will keep this first config forever.
@joeljstephen commented on GitHub (Apr 10, 2024):
@Breee I am unable to reproduce this issue. Can you let me know if this issue still exists for you in the latest build? If not, I will be closing this issue in a few days.
@Breee commented on GitHub (Apr 18, 2024):
Sorry for the late reply - the issue was resolved by clearing the frontend cache.
however, there should be some kind of cache invalidation from hoppscotch side - as i don't find it valid to force my users to clear their caches - that's just my opinion tho