github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-08 13:49:15 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #2488] Password protection not enforced in Authentication Methods #10935

New Issue
Closed
opened 2026-05-06 15:35:49 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-06 15:35:49 -05:00
Owner
Copy Link

Originally created by @jtechbyte on GitHub (Feb 16, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2488

Describe the Bug

When configuring password protection under the Authentication Methods section in Pangolin, the security layer is not being enforced.

After assigning a password to protect a resource, the application does not prompt for authentication and allows access without requiring the configured credentials.

Environment

  • OS Type & Version: (e.g., Ubuntu 22.04)
  • Pangolin Version: 1.15.4
  • Gerbil Version: 1.3.0
  • Traefik Version: 3.6.8
  • Newt Version: 1.9.0
  • Olm Version: (if applicable)

To Reproduce

  1. Navigate to Authentication Methods.
  2. Assign password protection to a resource.
  3. Attempt to access the protected resource.
  4. Observe that no authentication is required

Expected Behavior

Once password protection is enabled and configured, users should be required to authenticate before gaining access to the protected resource.

Originally created by @jtechbyte on GitHub (Feb 16, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2488 ### Describe the Bug When configuring password protection under the Authentication Methods section in Pangolin, the security layer is not being enforced. After assigning a password to protect a resource, the application does not prompt for authentication and allows access without requiring the configured credentials. ### Environment - OS Type & Version: (e.g., Ubuntu 22.04) - Pangolin Version: 1.15.4 - Gerbil Version: 1.3.0 - Traefik Version: 3.6.8 - Newt Version: 1.9.0 - Olm Version: (if applicable) ### To Reproduce 1. Navigate to Authentication Methods. 2. Assign password protection to a resource. 3. Attempt to access the protected resource. 4. Observe that no authentication is required ### Expected Behavior Once password protection is enabled and configured, users should be required to authenticate before gaining access to the protected resource.
GiteaMirror commented 2026-05-06 15:35:51 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Feb 25, 2026):

You likely already have a session. Try clearing the cookies or using incognito. I am unable to reproduce.

<!-- gh-comment-id:3961742504 --> @miloschwartz commented on GitHub (Feb 25, 2026): You likely already have a session. Try clearing the cookies or using incognito. I am unable to reproduce.
GiteaMirror commented 2026-05-06 15:35:51 -05:00
Author
Owner
Copy Link

@jtechbyte commented on GitHub (Feb 25, 2026):

Yeah I tried external browsers and I still get the login screen without the
extra layer of protection.

On Wed, Feb 25, 2026 at 3:09 PM Milo Schwartz @.***>
wrote:

Closed #2488 https://github.com/fosrl/pangolin/issues/2488 as completed.

—
Reply to this email directly, view it on GitHub
https://github.com/fosrl/pangolin/issues/2488#event-23080440144, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR74TAWLR5YR2DCOHTLEJ34NX6QDAVCNFSM6AAAAACVJSF3QKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRTGA4DANBUGAYTINA
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:3961933068 --> @jtechbyte commented on GitHub (Feb 25, 2026): Yeah I tried external browsers and I still get the login screen without the extra layer of protection. On Wed, Feb 25, 2026 at 3:09 PM Milo Schwartz ***@***.***> wrote: > Closed #2488 <https://github.com/fosrl/pangolin/issues/2488> as completed. > > — > Reply to this email directly, view it on GitHub > <https://github.com/fosrl/pangolin/issues/2488#event-23080440144>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAR74TAWLR5YR2DCOHTLEJ34NX6QDAVCNFSM6AAAAACVJSF3QKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRTGA4DANBUGAYTINA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#10935
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?