3 people 711d688294 fix(login): resolve the registration org consistently with the login policy (#12621) ...

# Which Problems Are Solved

When resolving the organization for a self-registration, the resource
owner was determined only from an explicitly requested org, falling back
to the default org. The login policy applied to the same request,
however, is resolved from the requested org, the user org, and only then
the default org. As a result the two could diverge — e.g. after the
login context had already resolved a user's organization — and a user
could be registered in a different organization than the one whose
settings were evaluated for the request.

# How the Problems Are Solved

`determineResourceOwner` now uses the same resolution order as the
policy lookup (requested org, then user org, then default org), so the
organization a user is registered in matches the one the request was
evaluated against.

# Additional Changes

Added a unit test covering the resolution order.

# Additional Context

Aligns login v1 registration org resolution with the behavior in login
v2.

Co-authored-by: Claude Opus 4.8 <[email protected]>

2026-08-28 10:37:52 +00:00

..

console

feat(telemetry): unify request details (#11509)

2026-03-18 14:07:33 +01:00

login

fix(login): resolve the registration org consistently with the login policy (#12621)

2026-08-28 10:37:52 +00:00