[GH-ISSUE #1455] OIDC only valid absolute URLs can be requested #411

Closed
opened 2026-02-26 18:46:56 +03:00 by kerem · 6 comments
Owner

Originally created by @Saddamus on GitHub (Nov 7, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1455

Originally assigned to: @ephraimduncan on GitHub.

Issue Description

Hello,
I have deployed the project with docker compose (production).
Have configured variables:

NEXTAUTH_URL="https://mycorrectdomain.swiss"
NEXT_PUBLIC_WEBAPP_URL="https://mycorrectdomain.swiss"

And

NEXT_PRIVATE_OIDC_WELL_KNOWN="https://MyKeycloakdomain.cloud/auth/realms/ClientsAuth/.well-known/openid-configuration"
NEXT_PRIVATE_OIDC_CLIENT_ID="documenso"
NEXT_PRIVATE_OIDC_CLIENT_SECRET="redacted"
NEXT_PRIVATE_OIDC_PROVIDER_LABEL="Keycloak"

When i try to login using openid, it doesnt work and docker-compose logs displays "...only valid absolute URLs can be requested"
Am i missing anything or maybe its due do .swiss domainm which doesnt pass validation as url ?

Steps to Reproduce

Setup documenso over docker-compose with keycloak as openid provider

Expected Behavior

Should work

Current Behavior

Doesnt work

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

Debian (docker)

Browser [e.g., Chrome, Firefox]

Firefox

Version [e.g., 2.0.1]

Latest

Please check the boxes that apply to this issue report.

  • I have searched the existing issues to make sure this is not a duplicate.
  • I have provided steps to reproduce the issue.
  • I have included relevant environment information.
  • I have included any relevant screenshots.
  • I understand that this is a voluntary contribution and that there is no guarantee of resolution.
  • I want to work on creating a PR for this issue if approved
Originally created by @Saddamus on GitHub (Nov 7, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1455 Originally assigned to: @ephraimduncan on GitHub. ### Issue Description Hello, I have deployed the project with docker compose (production). Have configured variables: ``` NEXTAUTH_URL="https://mycorrectdomain.swiss" NEXT_PUBLIC_WEBAPP_URL="https://mycorrectdomain.swiss" ``` And ``` NEXT_PRIVATE_OIDC_WELL_KNOWN="https://MyKeycloakdomain.cloud/auth/realms/ClientsAuth/.well-known/openid-configuration" NEXT_PRIVATE_OIDC_CLIENT_ID="documenso" NEXT_PRIVATE_OIDC_CLIENT_SECRET="redacted" NEXT_PRIVATE_OIDC_PROVIDER_LABEL="Keycloak" ``` When i try to login using openid, it doesnt work and docker-compose logs displays "...only valid absolute URLs can be requested" Am i missing anything or maybe its due do .swiss domainm which doesnt pass validation as url ? ### Steps to Reproduce Setup documenso over docker-compose with keycloak as openid provider ### Expected Behavior Should work ### Current Behavior Doesnt work ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] Debian (docker) ### Browser [e.g., Chrome, Firefox] Firefox ### Version [e.g., 2.0.1] Latest ### Please check the boxes that apply to this issue report. - [X] I have searched the existing issues to make sure this is not a duplicate. - [X] I have provided steps to reproduce the issue. - [X] I have included relevant environment information. - [ ] I have included any relevant screenshots. - [X] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved
kerem 2026-02-26 18:46:56 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Nov 7, 2024):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

<!-- gh-comment-id:2462695831 --> @github-actions[bot] commented on GitHub (Nov 7, 2024): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)
Author
Owner

@github-actions[bot] commented on GitHub (Nov 14, 2024):

🚨 Documenso Police 🚨

@ephraimduncan has 5 open issues assigned already. Consider whether this issue should be assigned to them or left open for another contributor.

<!-- gh-comment-id:2475852200 --> @github-actions[bot] commented on GitHub (Nov 14, 2024): ### 🚨 Documenso Police 🚨 @ephraimduncan has 5 open issues assigned already. Consider whether this issue should be assigned to them or left open for another contributor.
Author
Owner

@FrankSchoene commented on GitHub (Nov 23, 2024):

May I ask you where you got the list of ENV variables you are using? Like ....
NEXT_PRIVATE_OIDC_PROVIDER_LABEL=
I can`t find anything in the documentation except of the Google-Example.
Thanks in advance.

<!-- gh-comment-id:2495631845 --> @FrankSchoene commented on GitHub (Nov 23, 2024): May I ask you where you got the list of ENV variables you are using? Like .... NEXT_PRIVATE_OIDC_PROVIDER_LABEL= I can`t find anything in the documentation except of the Google-Example. Thanks in advance.
Author
Owner

@celevra commented on GitHub (Feb 5, 2025):

same issue here

@FrankSchoene see .env.example

<!-- gh-comment-id:2637030005 --> @celevra commented on GitHub (Feb 5, 2025): same issue here @FrankSchoene see .env.example
Author
Owner

@celevra commented on GitHub (Feb 5, 2025):

you have to remove the " after the =

use this:

NEXTAUTH_URL=https://mycorrectdomain.swiss
NEXT_PUBLIC_WEBAPP_URL=https://mycorrectdomain.swiss
<!-- gh-comment-id:2637113659 --> @celevra commented on GitHub (Feb 5, 2025): you have to remove the " after the = use this: ``` NEXTAUTH_URL=https://mycorrectdomain.swiss NEXT_PUBLIC_WEBAPP_URL=https://mycorrectdomain.swiss ```
Author
Owner

@ephraimduncan commented on GitHub (Aug 23, 2025):

@celevra is correct. Closing as this is a configuration issue, not a bug.

<!-- gh-comment-id:3216983154 --> @ephraimduncan commented on GitHub (Aug 23, 2025): @celevra is correct. Closing as this is a configuration issue, not a bug.
Sign in to join this conversation.
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/documenso#411
No description provided.