Unable to login via IdentityProvider Initiated #180

Closed
opened 2025-11-01 20:49:54 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @acelinkio on GitHub (Jan 8, 2024).

Description

I unable to login via identity provider (IDP) initiated. After clicking on launch icon inside of my identity provider, I am taken to the SP initiated login screen for Vikunja, https://tasks.mydomain.tld/login, instead of being logged into the application. Ideally that would automatically sign in to Vikunja.

Instead additional click is needed to start the service provider (SP) initiated login, which does work correctly.

Vakunja API Settings

config.yaml: |
  auth:
    openid:
      enabled: true
      redirecturl: https://tasks.mydomain.tld/auth/openid/
      providers:
        - name: authentik
          authurl: https://auth.mydomain.tld/application/o/vikunja/
          logouturl: https://auth.mydomain.tld/application/o/vikunja/end-session/
          clientid: vikunja
          clientsecret: "REDACTEDSECRETTOKEN"

Authentik version 2023.10.5
Settings configuration via Terraform

resource "authentik_provider_oauth2" "vikunja_ouath2" {
  name      = "vikunja"
  client_id = "vikunja"
  client_secret = "REDACTEDSECRETTOKEN"
  authorization_flow = data.authentik_flow.default-authorization-flow.id
  access_code_validity = "minutes=10"
  redirect_uris = [ "https://tasks.mydomain.tld/auth/openid/authentik"]
  signing_key = data.authentik_certificate_key_pair.generated.id
  property_mappings = [
    data.authentik_scope_mapping.openid.id,
    data.authentik_scope_mapping.email.id,
    data.authentik_scope_mapping.profile.id
  ]
}

resource "authentik_application" "vikunja_application" {
  name = authentik_provider_oauth2.vikunja_ouath2.name
  slug = authentik_provider_oauth2.vikunja_ouath2.name
  protocol_provider = authentik_provider_oauth2.vikunja_ouath2.id
  meta_icon = "https://kolaente.dev/avatars/dd73c49581a6904336c5d40fb66ef950?size=280"
  meta_launch_url = "https://tasks.mydomain.tld"
  policy_engine_mode = "all"
}

Vikunja Frontend Version

vikunja/frontend:0.22.0

Vikunja API Version

vikunja/api:0.22.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @acelinkio on GitHub (Jan 8, 2024). ### Description I unable to login via identity provider (IDP) initiated. After clicking on launch icon inside of my identity provider, I am taken to the SP initiated login screen for Vikunja, https://tasks.mydomain.tld/login, instead of being logged into the application. Ideally that would automatically sign in to Vikunja. Instead additional click is needed to start the service provider (SP) initiated login, which does work correctly. Vakunja API Settings ```yaml config.yaml: | auth: openid: enabled: true redirecturl: https://tasks.mydomain.tld/auth/openid/ providers: - name: authentik authurl: https://auth.mydomain.tld/application/o/vikunja/ logouturl: https://auth.mydomain.tld/application/o/vikunja/end-session/ clientid: vikunja clientsecret: "REDACTEDSECRETTOKEN" ``` Authentik version 2023.10.5 Settings configuration via Terraform ```hcl resource "authentik_provider_oauth2" "vikunja_ouath2" { name = "vikunja" client_id = "vikunja" client_secret = "REDACTEDSECRETTOKEN" authorization_flow = data.authentik_flow.default-authorization-flow.id access_code_validity = "minutes=10" redirect_uris = [ "https://tasks.mydomain.tld/auth/openid/authentik"] signing_key = data.authentik_certificate_key_pair.generated.id property_mappings = [ data.authentik_scope_mapping.openid.id, data.authentik_scope_mapping.email.id, data.authentik_scope_mapping.profile.id ] } resource "authentik_application" "vikunja_application" { name = authentik_provider_oauth2.vikunja_ouath2.name slug = authentik_provider_oauth2.vikunja_ouath2.name protocol_provider = authentik_provider_oauth2.vikunja_ouath2.id meta_icon = "https://kolaente.dev/avatars/dd73c49581a6904336c5d40fb66ef950?size=280" meta_launch_url = "https://tasks.mydomain.tld" policy_engine_mode = "all" } ``` ### Vikunja Frontend Version vikunja/frontend:0.22.0 ### Vikunja API Version vikunja/api:0.22.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
Author
Owner

@kolaente commented on GitHub (Jan 9, 2024):

This works as intended. If there are multiple auth methods, users need to be able to choose which one they use.

If you set the link to https://tasks.mydomain.tld/?redirectToProvider=true and have local auth disabled and have only one auth provider, it will automatically redirect the user to your Auth provider when they are not logged in.

This does not happen automatically because then users would be logged in again directly after they logged out.

@kolaente commented on GitHub (Jan 9, 2024): This works as intended. If there are multiple auth methods, users need to be able to choose which one they use. If you set the link to `https://tasks.mydomain.tld/?redirectToProvider=true` and have local auth disabled and have only one auth provider, it will automatically redirect the user to your Auth provider when they are not logged in. This does not happen automatically because then users would be logged in again directly after they logged out.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#180