You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful to be able pass additional data from the signup process to a handler for the registration webhook without utilising traits.
This could be used to implement this flow as an example, which stores a cookie consent given at signup in the metadata_public for the user:
Describe your ideal solution
Add an extra field to theUpdateRegistrationFlowWithPasswordMethod struct here.
Something like this:
typeUpdateRegistrationFlowWithPasswordMethodstruct {
// ...// Extra data to pass along to any webhooks//// required: falseExtra json.RawMessage`json:"extra"`
}
This field could be validated to contain well formed json and then passed as is to the webhook endpoint.
Workarounds or alternatives
Traits could be used but have some disadvantages:
traits are a permanent part of the schema although the data might be transient
traits will be stored in Kratos
users will be able to see and modify the traits
Version
v0.11.1
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Preflight checklist
Describe your problem
It would be helpful to be able pass additional data from the signup process to a handler for the registration webhook without utilising traits.
This could be used to implement this flow as an example, which stores a cookie consent given at signup in the

metadata_public
for the user:Describe your ideal solution
Add an extra field to the
UpdateRegistrationFlowWithPasswordMethod
struct here.Something like this:
This field could be validated to contain well formed json and then passed as is to the webhook endpoint.
Workarounds or alternatives
Traits could be used but have some disadvantages:
Version
v0.11.1
Additional Context
No response
The text was updated successfully, but these errors were encountered: