[Bug]: OIDC - Cannot Decode JWTs #2834

Closed
opened 2026-04-25 00:11:05 +02:00 by adam · 8 comments
Owner

Originally created by @slinky34 on GitHub (Jun 9, 2025).

What happened?

Hi, Im using Authenik with Audiobookshelf. I go to my authentik lading page, I click ABS and get and unauthorized error. I have tried this using an existing user in ABS and a new user.

Checking the error logs in ABS, I see the following I get a RPE error, that says JWTs, Can't be decoded.

What did you expect to happen?

Expecting that once I click ABS, it logs me in via Authenik ODIC.

Steps to reproduce the issue

  1. Go to authenik lading/home Page
  2. Click ABS application
  3. Slect Login with Authenik
  4. get Error

Audiobookshelf version

v2.24.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

2025-06-09 17:15:15.902

ERROR

"[Auth] No data in openid callback - RPError: failed to decode JWT (TypeError: encrypted JWTs cannot be decoded)"

2025-06-09 17:16:27.345

ERROR

"[Auth] No data in openid callback - RPError: failed to decode JWT (TypeError: encrypted JWTs cannot be decoded)"

2025-06-09 17:16:33.454

ERROR

"[Auth] No data in openid callback - RPError: failed to decode JWT (TypeError: encrypted JWTs cannot be decoded)"

2025-06-09 17:17:12.420

ERROR

"[Auth] No data in openid callback - RPError: failed to decode JWT (TypeError: encrypted JWTs cannot be decoded)"

Additional Notes

No response

Originally created by @slinky34 on GitHub (Jun 9, 2025). ### What happened? Hi, Im using Authenik with Audiobookshelf. I go to my authentik lading page, I click ABS and get and unauthorized error. I have tried this using an existing user in ABS and a new user. Checking the error logs in ABS, I see the following I get a RPE error, that says JWTs, Can't be decoded. ### What did you expect to happen? Expecting that once I click ABS, it logs me in via Authenik ODIC. ### Steps to reproduce the issue 1. Go to authenik lading/home Page 2. Click ABS application 3. Slect Login with Authenik 4. get Error ### Audiobookshelf version v2.24.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 2025-06-09 17:15:15.902 ERROR "[Auth] No data in openid callback - RPError: failed to decode JWT (TypeError: encrypted JWTs cannot be decoded)" 2025-06-09 17:16:27.345 ERROR "[Auth] No data in openid callback - RPError: failed to decode JWT (TypeError: encrypted JWTs cannot be decoded)" 2025-06-09 17:16:33.454 ERROR "[Auth] No data in openid callback - RPError: failed to decode JWT (TypeError: encrypted JWTs cannot be decoded)" 2025-06-09 17:17:12.420 ERROR "[Auth] No data in openid callback - RPError: failed to decode JWT (TypeError: encrypted JWTs cannot be decoded)" ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:11:05 +02:00
adam closed this issue 2026-04-25 00:11:06 +02:00
Author
Owner

@nichwall commented on GitHub (Jun 9, 2025):

Did you verify all settings on both Authentik and Audiobookshelf side? You will need to restart the ABS server for OIDC changes to take effect.

https://www.audiobookshelf.org/guides/oidc_authentication

@nichwall commented on GitHub (Jun 9, 2025): Did you verify all settings on both Authentik and Audiobookshelf side? You will need to restart the ABS server for OIDC changes to take effect. https://www.audiobookshelf.org/guides/oidc_authentication
Author
Owner

@slinky34 commented on GitHub (Jun 10, 2025):

Yes, my settings match on both ends, I used the auto-populate option in ABS with the Issuer URL from Authentik.

@slinky34 commented on GitHub (Jun 10, 2025): Yes, my settings match on both ends, I used the auto-populate option in ABS with the Issuer URL from Authentik.
Author
Owner

@nichwall commented on GitHub (Jun 10, 2025):

Does the signing algorithm match?

@nichwall commented on GitHub (Jun 10, 2025): Does the signing algorithm match?
Author
Owner

@slinky34 commented on GitHub (Jun 10, 2025):

Yes

Image

@slinky34 commented on GitHub (Jun 10, 2025): Yes ![Image](https://github.com/user-attachments/assets/e7ac06cb-b51f-4849-8d47-781a4b0c86be)
Author
Owner

@nichwall commented on GitHub (Jun 10, 2025):

Have you only enabled token signing in Authentik, or did you also enable token encryption?

@nichwall commented on GitHub (Jun 10, 2025): Have you only enabled token signing in Authentik, or did you also enable token encryption?
Author
Owner

@slinky34 commented on GitHub (Jun 10, 2025):

Image

Image

my Authentik provider settings

@slinky34 commented on GitHub (Jun 10, 2025): ![Image](https://github.com/user-attachments/assets/ffaa32f3-d186-4e51-8141-2877c915433e) ![Image](https://github.com/user-attachments/assets/388760d8-4661-498c-a573-ce228025a126) my Authentik provider settings
Author
Owner

@Sapd commented on GitHub (Jun 10, 2025):

my Authentik provider settings

Well you provided an Encryption key. It must be set to nothing. "encrypted JWTs cannot be decoded"

@Sapd commented on GitHub (Jun 10, 2025): > my Authentik provider settings Well you provided an Encryption key. It must be set to nothing. "encrypted JWTs cannot be decoded"
Author
Owner

@slinky34 commented on GitHub (Jun 11, 2025):

Well I feel silly! Thank you! That worked :)

@slinky34 commented on GitHub (Jun 11, 2025): Well I feel silly! Thank you! That worked :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2834