Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Active field should not be required for Kratos registration #14

Closed
AntiSC2 opened this issue May 9, 2020 · 0 comments · Fixed by ory/kratos#401
Closed

Active field should not be required for Kratos registration #14

AntiSC2 opened this issue May 9, 2020 · 0 comments · Fixed by ory/kratos#401

Comments

@AntiSC2
Copy link

AntiSC2 commented May 9, 2020

Kratos version: v0.2.1-alpha.1
Oathkeeper version: v0.38.1-beta.1
SDK version: Python 0.2.1a1

When calling:
api_response = api_instance.get_self_service_browser_registration_request(request)
I get the following exception:
Invalid value for 'active', must not be 'None'
This is the same problem as #10 and #11 and I think the solution here is the same.

The following line is the one that causes the problem: https://github.com/ory/kratos/blob/master/selfservice/flow/registration/request.go#L45

omitempty-flag is set but required true is also set so an exception is thrown in the Python SDK when it is omitted. The solution is probably to remove required: true. Strangely, this is only set for the registration flow, not any other flow and I don't know if you can set this active property. I don't see anything about it in the documentation. Also the active property documentation in the SDK seems a bit broken, it just says:

and so on.

AntiSC2 added a commit to AntiSC2/kratos that referenced this issue May 9, 2020
Closes ory/sdk#14

Signed-off-by: Jakob Sinclair <sinclair.jakob@mailbox.org>
aeneasr pushed a commit to ory/kratos that referenced this issue May 11, 2020
Closes ory/sdk#14

Signed-off-by: Jakob Sinclair <sinclair.jakob@mailbox.org>
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 a pull request may close this issue.

1 participant