Allow disabling automatically added verification hook on registration

[David-Wobrock]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe your problem

With our usage of Kratos, we have email verification enabled because we allow doing it in certain circumstances.

However, we do not want to trigger email verification post-registration (the same applies to post-settings, but we don't use it).

We would like a way to disable injected the email verification hook, but still keep the email verification feature globally enabled.

kratos/driver/registry_default_registration.go

Lines 38 to 41 in 2cc2b69

	// WARNING - If you remove this, no verification emails / sms will be sent post-registration.
	if m.Config().SelfServiceFlowVerificationEnabled(ctx) {
	hooks = slices.Insert(hooks, 0, registration.PostHookPostPersistExecutor(m.HookVerifier()))
	}

Describe your ideal solution

If we didn't take into account any past, the ideal solution would be that no hooks are added by the code in a hard-coded manner, but that the hooks need to be configured manually.

However, to avoid introducing a breaking change, I guess introducing a new config variable that allows disabling this automatic adding of the hook would be best.

Workarounds or alternatives

In our current forked version of Kratos, we plainly removed adding the LOC that adds the hook.

Version

v1.3.1

Additional Context

No response

[github-actions]

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas on how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

[David-Wobrock]

Opened PR related to this: #4577