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
Fix loadIdentifier called after loadAuthenticator losing resolver config
When loadAuthenticator() was called before loadIdentifier(), the
authenticator would receive an empty IdentifierCollection and create
its own default Password identifier immediately in the constructor.
Later calls to loadIdentifier() would add to the service's identifier
collection, but the authenticator already had its own separate
collection with the default identifier.
This fix changes the default identifier loading from eager (in
constructor) to lazy (in authenticate()). This ensures that if
loadIdentifier() is called after loadAuthenticator(), the identifier
will be loaded into the shared collection before the authenticator
tries to use it.
Fixes#754
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
0 commit comments