Skip to content

Conversation

@camero2734
Copy link

@camero2734 camero2734 commented Oct 17, 2025

After #4402 was merged, there is no way to get the verification UI to show after the user changes their email.

It seems this was intended, as it's even documented here:
https://www.ory.com/docs/actions/require-verified-address#show-verification-screen-after-address-change

But if you actually configure this (when self-hosting), you get an error that that hook isn't allowed there (I got this both in the officially released oryd/kratos:v1.3.1 image, as well as in a custom build based off of the master branch)

I regenerated the schema via ./script/render-schemas.sh. After this change, the following is now allowed as expected:

selfservice:
  flows:
    settings:
      after:
        profile:
          hooks:
            - hook: show_verification_ui

Related issue(s)

#4402

Checklist

  • I have read the contributing guidelines.
  • I have referenced an issue containing the design document if my change
    introduces a new feature.
  • I am following the
    contributing code guidelines.
  • I have read the security policy.
  • I confirm that this pull request does not address a security
    vulnerability. If this pull request addresses a security vulnerability, I
    confirm that I got the approval (please contact
    [email protected]) from the maintainers to push
    the changes.
  • I have added tests that prove my fix is effective or that my feature
    works.
  • I have added or changed the documentation.

@camero2734 camero2734 changed the title Allow show_verification_ui for flows.settings.after.profile.hooks fix: allow show_verification_ui for flows.settings.after.profile.hooks Oct 17, 2025
@camero2734 camero2734 marked this pull request as ready for review October 17, 2025 11:34
@camero2734 camero2734 requested review from a team and aeneasr as code owners October 17, 2025 11:34
@camero2734 camero2734 force-pushed the allow-show-verification-ui-profile branch from 314d97a to 00a7418 Compare October 17, 2025 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant