Skip to content

Conversation

@lol768
Copy link

@lol768 lol768 commented Oct 9, 2025

There is no sign of support for doing what was described in the documentation. The config schema suggests only "webhook" is allowed in definitions/selfServiceAfterSettingsMethod. In Kratos, I also do not see any sign of a ExecuteSettingsPostPersistHook method in address_verifier.go so do not understand how this could have ever worked.

This appears to have tripped multiple people up: https://ory-community.slack.com/archives/C0522079BS5/p1753886141446629?thread_ts=1753886038.426959&cid=C0522079BS5

There is no sign of support for doing what was described in the documentation. The config schema suggests only "webhook" is allowed in definitions/selfServiceAfterSettingsMethod. In Kratos, I also do not see any sign of a ExecuteSettingsPostPersistHook method in address_verifier.go so do not understand how this could have ever worked.
@lol768 lol768 requested review from aeneasr and vinckr as code owners October 9, 2025 11:33
@lol768 lol768 changed the title Remove unsupported settings hook from verified address docs chore(docs): Remove unsupported settings hook from verified address docs Oct 9, 2025
@lol768
Copy link
Author

lol768 commented Oct 9, 2025

Copy link
Member

@zepatrik zepatrik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems this was introduced but is not yet released officially in open source. What version of Kratos are you running?
ory/kratos@c433c44

@lol768
Copy link
Author

lol768 commented Oct 9, 2025

Thanks, that's useful context (had missed that diff when looking through the codebase) - running latest available tagged v1.3.1.

Is it worth covering this in the documentation?

@zepatrik
Copy link
Member

zepatrik commented Oct 9, 2025

We're working on improving versioning and the split between Ory Network and Open Source versions, so while it is confusing right now, we will hopefully have a better docs structure in the future that makes this clear. I'll close this PR then.

@zepatrik zepatrik closed this Oct 9, 2025
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 this pull request may close these issues.

2 participants