User data migrated although password validation endpoint (POST) returns response with status NOT 200

[daniel-frak]

User data migrated although password validation endpoint (POST) returns response with status NOT 200

[daniel-frak]

Indeed, both LegacyProvider::getUserByUsername and LegacyProvider::getUserByEmail call UserModelFactory::create, which then creates the user in Keycloak and sets up a federation link to the legacy system - that way only the credentials will get verified against the legacy system in the future, with no need to make the GET call (for user details) again .

Once the user logs in successfully, LegacyProvider::updateCredential gets called, severing the link to the legacy system entirely.

Is there anything in the plugin's behavior that's preventing your migration from going smoothly?

EDIT: I have updated the README.md example to better describe what is happening behind the scenes when a user logs in.

[swc-kdzekov]

Hi @daniel-frak . Yes, this confirms what I assumed. With updated description it is even more clear.

[Is there anything in the plugin's behavior that's preventing your migration from going smoothly?]

No, It works quite nicely actually. We tested it with hard-coded data up to now (which is enough).
Thanks.

[daniel-frak]

Glad to have helped! :)