[GH-ISSUE #957] Feature Request: Ability to Disable Authentication #2105

New issue

Closed

opened 2026-03-01 17:56:32 +03:00 by kerem · 1 comment

kerem commented

2026-03-01 17:56:32 +03:00

Owner

Originally created by @vorpalhex on GitHub (Mar 28, 2022).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/957

Having good secure authentication by default is the correct thing. However, many authentication situations such as reverse-proxy authentication or vpn based access means authentication is already occurring before we even get to Archivebox. Hopefully over time ArchiveBox will work with some of these (such as the WIP reverse proxy support) but in the meantime it would be tremendously useful to be able to disable authentication entirely and just dump users into a default profile with admin abilities. ArchiveBox is never going to be able to support ever auth pattern under the sun - and in many single user cases it doesn't need to.

This should come with the appropriate warnings and flags, the usual encouragement to not do such a thing and so on. However, it should be possible.

I'm a single user instance of archivebox. It's lan accessible, wrapped behind a reverse proxy and so on. Having a double login screen is really painful for me as a user, especially as much of my usage is on mobile.

Originally created by @vorpalhex on GitHub (Mar 28, 2022). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/957 Having good secure authentication by default is the correct thing. However, many authentication situations such as reverse-proxy authentication or vpn based access means authentication is already occurring before we even get to Archivebox. Hopefully over time ArchiveBox will work with some of these (such as the WIP reverse proxy support) but in the meantime it would be tremendously useful to be able to disable authentication entirely and just dump users into a default profile with admin abilities. ArchiveBox is never going to be able to support ever auth pattern under the sun - and in many single user cases it doesn't need to. This should come with the appropriate warnings and flags, the usual encouragement to not do such a thing and so on. However, it should be possible. I'm a single user instance of archivebox. It's lan accessible, wrapped behind a reverse proxy and so on. Having a double login screen is really painful for me as a user, especially as much of my usage is on mobile.

kerem

2026-03-01 17:56:32 +03:00

closed this issue
added the
status: idea-phase
label

kerem commented

2026-03-01 17:56:33 +03:00

Author

Owner

@pirate commented on GitHub (Mar 30, 2022):

Already in progress: https://github.com/ArchiveBox/ArchiveBox/pull/866 #773, for now use:

archivebox config --set PUBLIC_INDEX=True
archivebox config --set PUBLIC_SNAPSHOTS=True
archivebox config --set PUBLIC_ADD_VIEW=True

@pirate commented on GitHub (Mar 30, 2022): Already in progress: https://github.com/ArchiveBox/ArchiveBox/pull/866 #773, for now use: ``` archivebox config --set PUBLIC_INDEX=True archivebox config --set PUBLIC_SNAPSHOTS=True archivebox config --set PUBLIC_ADD_VIEW=True ```

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ArchiveBox#2105

No description provided.

Rows
Columns