Setting up a Criteria for self-service registration

[xxsuperdreamxx]

The feature is meant to set custom criteria for the registration form, for example setting up a dob (date of birth) field, to prevent underage users to register to the product, because of the "COPPA".

I have considered just putting in the schema field type "number" with the name age and set the minimum, but it would also be nice to be able to apply cookie, but also instead of using the number filed to use the date

If someone has a good suggestion or solution, I would be happy to hear it out. Because the easiest thing now I am thinking about is to do the limitation in the front end, but I don't think that is enough

[aeneasr]

Thank you for contributing to this repository by creating an issue!

Unfortunately, your issue lacks vital information, such as log files, the error message, the software version, your configuration or other pieces of the puzzle.

Please also ensure that your issue is appropriately formatted. If you do not know how to write markdown, you can find help here.

Helping you with your problem is only possible if you share this information, and it will save a lot of time of back and forth on your as well as our end!

For this reason, this repository uses issue templates which you can select when pressing "New issue". Please use one of those issue templates to fill in the required information. You can either create a new issue for this purpose and close this one, or leave a comment.

If you have used an issue template and see this comment, it means that your description lacks information that allows maintainers to understand what problem you are facing and how to reproduce it.

Do not edit the original post as we will not be notified when you do so.

If you do not provide the requested information, this issue will be closed. Thank you for your understanding!

---

In particular: example payloads, what you have tried so far, why webhooks are not an option for you, …

[harnash]

@xxsuperdreamxx It may be an overkill in some cases and perhaps an easier solution can be ironed out but #1585 gives the possibility to implement checks in via the hooks and propagate validation errors to the frontend. It is still not ideal and I'm looking for a time to wrap it all up but this is essentially what we are doing right now since our checks are quite complex.

[xxsuperdreamxx]

I absolutely understand, I really like Ory and I would love to use it as a daily driver and because I am also a university student, we also need to comply with the current laws for our projects and it was going to be really nice to use Ory Kratos, so I can save couple of nerves haha, since Go language is wayyy better that Java haha

…

On Wed, 8 Sept 2021 at 21:18, Łukasz Harasimowicz ***@***.***> wrote: @xxsuperdreamxx <https://github.com/xxsuperdreamxx> It may be an overkill in some cases and perhaps an easier solution can be ironed out but #1585 <#1585> gives the possibility to implement checks in via the hooks and propagate validation errors to the frontend. It is still not ideal and I'm looking for a time to wrap it all up but this is essentially what we are doing right now since our checks are quite complex. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1724 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE2N3EHYINQIMQCF2CSZBIDUA6SHDANCNFSM5DMGVPPA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- “No matter how dark the night, morning always comes, and our journey begins anew.”― Lulu Final Fantasy X