Skip to content

[Bug]: OAauth authRequestsIds from the Zitadel API are not handled anymore since they have no "oidc_" prefix #454

Open
@Diginut-GmbH

Description

@Diginut-GmbH

Preflight Checklist

  • I could not find a solution in the documentation, the existing issues or discussions
  • I have joined the ZITADEL chat

Version

No response

Describe the problem caused by this bug

I am triggering an OAuth flow like described here: https://zitadel.com/docs/guides/integrate/login-ui/oidc-standard.

Like described in the documentation, the Zitadel API returns me an authRequestId like V2_224908753244265546 (prefixed with "V2_"). But the login app of the latest version (commit sha of main: d5695a0) only handles authRequestIds prefixed with saml_ or oidc_. See:

if (requestId.startsWith("oidc_")) {

To reproduce

Steps to reproduce:

  1. Get an authRequestId like:
https://login.example.com/oauth/v2/authorize?client_id=170086824411201793%40yourapp&redirect_uri=https%3A%2F%2Fyourapp.example.com%2Fauth%2Fcallback&response_type=code&scope=openid%20email%20profile&code_challenge=9az09PjcfuENS7oDK7jUd2xAWRb-B3N7Sr3kDoWECOY&code_challenge_method=S256&login_hint=minnie-mouse
  1. Use the authRequestId to login the user like:
https://login.example.com/loginname?organization=<organizationId>&client=<clientId>&requestId=<authRequestId>&state=<state>

Also see: https://zitadel.com/docs/guides/integrate/login-ui/oidc-standard

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    Status

    🧐 Investigating

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions