https://www.ory.sh/ logo
Join Slack
Powered by
For testing purposes I removed OIDC from a user th...
# ory-network
f
For testing purposes I removed OIDC from a user that already had password setup. When signing in with OIDC (to get to the account linking) after the removal I don’t seem to get to the linking step at all. We have two webhooks configured for after registration but I only get the first one where the identity id is basically: 
'00000000-0000-0000-0000-000000000000'
for which we return 200. I can’t see any failed calls either in the logs (only old events which are unrelated). The identity in question is 
8e2f03b0-b6df-420e-a5e1-8b73a6447e7b
any idea?
@bland-eye-99092 Do you need any more information to be able to assist, please let me know
Still having this issue and not really able to debug since the webhooks says nothing from the Ory page.
b
can you post the configuration for your webhook?
f
b
I do not have access to that, please post a screenshot with redacted information or the output from the CLI (redacted)
f
Copy code
registration:
      after:
        code:
          hooks:
          - hook: session
        default_browser_return_url: redacted/verify-email
        hooks: []
        oidc:
          default_browser_return_url: redacted/login-redirect
          hooks:
          - hook: session
          - config:
              auth:
                config:
                  password: redacted
                  user: redacted
                type: basic_auth
              body: redacted
              can_interrupt: false
              method: POST
              response:
                ignore: false
                parse: true
              url: redacted
            hook: web_hook
          - config:
              auth:
                config:
                  password: redacted
                  user: redacted
                type: basic_auth
              body: redacted
              can_interrupt: false
              method: POST
              response:
                ignore: true
                parse: false
              url: redacted
            hook: web_hook
        passkey:
          hooks:
          - hook: session
        password:
          hooks:
          - config:
              auth:
                config:
                  password: redacted
                  user: redacted
                type: basic_auth
              body: redacted
              can_interrupt: false
              method: POST
              response:
                ignore: false
                parse: true
              url: redacted
            hook: web_hook
          - config:
              auth:
                config:
                  password: redacted
                  user: redacted
                type: basic_auth
              body: redacted
              can_interrupt: false
              method: POST
              response:
                ignore: true
                parse: false
              url: redacted
            hook: web_hook
          - hook: session
        webauthn:
          hooks:
          - hook: session
          - config:
              auth:
                config:
                  password: redacted
                  user: redacted
                type: basic_auth
              body: redacted
              can_interrupt: false
              method: POST
              response:
                ignore: false
                parse: true
              url: redacted
            hook: web_hook
          - config:
              auth:
                config:
                  password: redacted
                  user: redacted
                type: basic_auth
              body: redacted
              can_interrupt: false
              method: POST
              response:
                ignore: true
                parse: false
              url: redacted
            hook: web_hook
b
And this is for an existing identity, where you're trying to reach the account linking?
f
Yes
I can login with username/password for this user.
b
That's not a registration flow, but a login flow, since the user already exists.
f
Hmm, not getting a login call though.
Like I do for all other users
b
not getting a login call though.
what call are you expecting?
f
Copy code
login:
      after:
        code:
          hooks: []
        default_browser_return_url: redacted
        hooks:
        - config:
            auth:
              config:
                password: redacted
                user: redacted
              type: basic_auth
            body: redacted
            can_interrupt: false
            method: POST
            response:
              ignore: true
              parse: false
            url: redacted
          hook: web_hook
That the user got login
b
could you try moving the hook definition to the password section?
f
But I login with SSO? But sure.
I am a bit confused though @bland-eye-99092. I am getting 1 out of two webhook calls on the registration endpoint when i “register/login” with SSO.
b
sorry I meant oidc.
f
No matter the webhooks, I dont get the account linked at all? Even after sign in
Normally we get both webhook calls on the registration for oidc when someone wants to link and we are able to perform the link. Something seems to happen for this user that breaks that.
b
Could you post a screencast of what's happening? Normally you would get the account linking screen if the account already exists, but you're trying to log in through OIDC.
f
Aaah, it seems like the return code from the API (to indicate account linking) in this flow has changed. Hence our custom ui flow for this is no longer rendering as it should.
Maybe this has been communicated somewhere and we have missed it?
b
I don't think it has, we adjusted the messages a little bit, but no status codes have changed.
f
Hmm.. that is weird because I dont see a change of this the last year when we built it
Open in Slack
PreviousNext
Powered by