starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Bug]: autolaunch=0 for SSO misconfiguration doesn't work #2671

New Issue
Closed
opened 2026-04-25 00:09:29 +02:00 by adam · 8 comments
adam commented 2026-04-25 00:09:29 +02:00
Owner
Copy Link
Copy Source

Originally created by @Aevaris on GitHub (Mar 19, 2025).

What happened?

Hi, in the documentation it notes:

In the case of a misconfiguration or an issue with SSO, it may be helpful to bypass SSO in favor of local login. Local login is possible while SSO redirect is enabled by manually navigating to https://abs.yoursite.com/login/?autoLaunch=0

But this does not actually work, OIDC is still forced regardless of this setting.
Image

Due to some challenges, where my auth server was located doesnt exist anymore so I need to reconfigure the ABS side of OIDC but cant log in to do so as there is no username/password field and no way to re-enable username login.

What did you expect to happen?

Have a login page

Steps to reproduce the issue

  1. Set up OIDC, disable username authentication, change your OIDC provider

Audiobookshelf version

2.20.0

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

If the issue is being seen in the UI, what browsers are you seeing the problem on?

Chrome

Logs

Additional Notes

No response

Originally created by @Aevaris on GitHub (Mar 19, 2025). ### What happened? Hi, in [the documentation](https://www.audiobookshelf.org/guides/oidc_authentication/) it notes: > In the case of a misconfiguration or an issue with SSO, it may be helpful to bypass SSO in favor of local login. Local login is possible while SSO redirect is enabled by manually navigating to https://abs.yoursite.com/login/?autoLaunch=0 But this does not actually work, OIDC is still forced regardless of this setting. ![Image](https://github.com/user-attachments/assets/261da280-7c62-45a2-b314-7529eaa70e5c) Due to some challenges, where my auth server was located doesnt exist anymore so I need to reconfigure the ABS side of OIDC but cant log in to do so as there is no username/password field and no way to re-enable username login. ### What did you expect to happen? Have a login page ### Steps to reproduce the issue 1. Set up OIDC, disable username authentication, change your OIDC provider ### Audiobookshelf version 2.20.0 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Linux ### If the issue is being seen in the UI, what browsers are you seeing the problem on? Chrome ### Logs ```shell ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:09:29 +02:00
adam closed this issue 2026-04-25 00:09:29 +02:00
adam commented 2026-04-25 00:09:30 +02:00
Author
Owner
Copy Link
Copy Source

@Aevaris commented on GitHub (Mar 19, 2025):

Nevermind, i misunderstood what this did. My issue is that i had disabled password auth and broke OIDC so couldnt log in to fix OIDC.

In case anyone runs into this, I:

  1. Verified I had a recent backup
  2. Docker compose down
  3. Docker system prune -a (to get rid of all non-permanent data)
  4. Renamed the config directory
  5. Docker compose pull && docker compose up -d
  6. Created a new admin account
  7. Restored from back up
  8. Fixed my OIDC on the ABS side

This got me back up and running like normal within ~10min

@Aevaris commented on GitHub (Mar 19, 2025): Nevermind, i misunderstood what this did. My issue is that i had disabled password auth and broke OIDC so couldnt log in to fix OIDC. In case anyone runs into this, I: 1. Verified I had a recent backup 2. Docker compose down 3. Docker system prune -a (to get rid of all non-permanent data) 4. Renamed the config directory 5. Docker compose pull && docker compose up -d 6. Created a new admin account 7. Restored from back up 8. Fixed my OIDC on the ABS side This got me back up and running like normal within ~10min
adam commented 2026-04-25 00:09:31 +02:00
Author
Owner
Copy Link
Copy Source

@DesertCookie commented on GitHub (Oct 16, 2025):

Hi, could you elaborate on how you restored from your backup?

Wouldn't restoring from backup also restore the old config with the broken SSO?

@DesertCookie commented on GitHub (Oct 16, 2025): Hi, could you elaborate on how you restored from your backup? Wouldn't restoring from backup also restore the old config with the broken SSO?
adam commented 2026-04-25 00:09:31 +02:00
Author
Owner
Copy Link
Copy Source

@Vito0912 commented on GitHub (Oct 16, 2025):

Then you need to edit the db of one of the backups and enable local Auth again.
I am not sure which table exactly, but iirc it should be serverSettings

@Vito0912 commented on GitHub (Oct 16, 2025): Then you need to edit the db of one of the backups and enable local Auth again. I am not sure which table exactly, but iirc it should be serverSettings
adam commented 2026-04-25 00:09:31 +02:00
Author
Owner
Copy Link
Copy Source

@DesertCookie commented on GitHub (Oct 17, 2025):

I removed all OID-related settings in the settings table, which caused the regular login to become functional again.

@DesertCookie commented on GitHub (Oct 17, 2025): I removed all OID-related settings in the `settings` table, which caused the regular login to become functional again.
adam commented 2026-04-25 00:09:31 +02:00
Author
Owner
Copy Link
Copy Source

@samumatic commented on GitHub (Nov 5, 2025):

There should be an adhoc sql command, that you can execute with docker exec to re-enable the local auth, like in #4675.

@samumatic commented on GitHub (Nov 5, 2025): There should be an adhoc sql command, that you can execute with docker exec to re-enable the local auth, like in #4675.
adam commented 2026-04-25 00:09:32 +02:00
Author
Owner
Copy Link
Copy Source

@MRobi1 commented on GitHub (Nov 6, 2025):

@DesertCookie can you share how you edited the DB?
Started having login issues with OIDC after 1yr+ so I don't have a backup that's that old that I can restore from.

@MRobi1 commented on GitHub (Nov 6, 2025): @DesertCookie can you share how you edited the DB? Started having login issues with OIDC after 1yr+ so I don't have a backup that's that old that I can restore from.
adam commented 2026-04-25 00:09:32 +02:00
Author
Owner
Copy Link
Copy Source

@DesertCookie commented on GitHub (Nov 6, 2025):

@DesertCookie can you share how you edited the DB?

I asked Google Gemini for assistance once I entered the container via Portainer. It gave me commands to list all database tables. Then to list all data within the settings table. Then I reset every OID setting in there to an empty string which resulted in the regular login working again.

@DesertCookie commented on GitHub (Nov 6, 2025): > [@DesertCookie](https://github.com/DesertCookie) can you share how you edited the DB? I asked Google Gemini for assistance once I entered the container via Portainer. It gave me commands to list all database tables. Then to list all data within the settings table. Then I reset every OID setting in there to an empty string which resulted in the regular login working again.
adam commented 2026-04-25 00:09:32 +02:00
Author
Owner
Copy Link
Copy Source

@MRobi1 commented on GitHub (Nov 7, 2025):

Thank you!
That was way harder than it needed to be. Gemini led me down the wrong path more than once.....
For future users.... I first had to get a version of sqlite that was 3.44+

#stop docker container
docker compose down

cd /config
#backup database file
cp absdatabase.sqlite absdatabase.sqlite.bak

#manually install sqlite 3.44+
wget https://sqlite.org/2024/sqlite-tools-linux-x64-3450000.zip
unzip sqlite-tools-linux-x64-3450000.zip
chmod +x sqlite3
mv sqlite3 sqlite3_latest

#access the database
./sqlite3_latest absdatabase.sqlite

#set all OIDC settings to null
UPDATE settings SET value = json_remove(value, '$.authOpenIDIssuerURL', '$.authOpenIDAuthorizationURL', '$.authOpenIDTokenURL', '$.authOpenIDUserInfoURL', '$.authOpenIDJwksURL', '$.authOpenIDLogoutURL', '$.authOpenIDClientID', '$.authOpenIDClientSecret', '$.authOpenIDTokenSigningAlgorithm', '$.authOpenIDButtonText') WHERE key = 'server-settings';
.exit

#restart docker container
docker compose up -d

Now that I can get back in... time to try to setup OIDC again and figure out why it suddenly stopped working on me.

@MRobi1 commented on GitHub (Nov 7, 2025): Thank you! That was way harder than it needed to be. Gemini led me down the wrong path more than once..... For future users.... I first had to get a version of sqlite that was 3.44+ ``` #stop docker container docker compose down cd /config #backup database file cp absdatabase.sqlite absdatabase.sqlite.bak #manually install sqlite 3.44+ wget https://sqlite.org/2024/sqlite-tools-linux-x64-3450000.zip unzip sqlite-tools-linux-x64-3450000.zip chmod +x sqlite3 mv sqlite3 sqlite3_latest #access the database ./sqlite3_latest absdatabase.sqlite #set all OIDC settings to null UPDATE settings SET value = json_remove(value, '$.authOpenIDIssuerURL', '$.authOpenIDAuthorizationURL', '$.authOpenIDTokenURL', '$.authOpenIDUserInfoURL', '$.authOpenIDJwksURL', '$.authOpenIDLogoutURL', '$.authOpenIDClientID', '$.authOpenIDClientSecret', '$.authOpenIDTokenSigningAlgorithm', '$.authOpenIDButtonText') WHERE key = 'server-settings'; .exit #restart docker container docker compose up -d ``` Now that I can get back in... time to try to setup OIDC again and figure out why it suddenly stopped working on me.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2671
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?