How to disable sending verification email after registration?

renom commented 1 year ago

Preflight checklist

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

Describe your problem

How to set up Ory Kratos to not having verification email sent automatically after registration?

Describe your ideal solution

Email verification is enabled, but verification emails aren't automatically sent after registration.

Workarounds or alternatives

-

Version

v0.11.1

Additional Context

No response

jonas-jonas commented 1 year ago

This is not possible, yet. But definitely something to think about implementing. What's your use case?

renom commented 1 year ago

We're sending a code (without an activation link), then the flow should be continued somehow, but we don't have a flow id. So we want to initiate the code flow manually, so then we'll have a flow id. The other solution could be returning a verification flow id in the last step of the registration flow.

jonas-jonas commented 1 year ago

The other solution could be returning a verification flow id in the last step of the registration flow.

We are working on that, too: https://github.com/ory/kratos/pull/3144

Should be ready soon, as well.

github-actions[bot] commented 1 month ago

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 🙏✌️

ory / kratos