Recently we have modified our login services (SAML Authentification) to go from on-premise ADFS to Azure ADFS.
After many emails with our IT department (who handles the Active Directory) we finally managed to update the Assertion Attributes Mapping with our application.
Everything was working fine with the plugin on the on-premise ADFS app. Since we've updated with the Azure ADFS there's a new error :
[EDIT] : Error message is : username X has already been taken. email X has already been taken
It seems like the plugin try to save the User before trying to log in ? Now if I delete the user in craft it re-create it just fine then login. If I logout then try to log in again the error will trigger.
Hi !
Recently we have modified our login services (SAML Authentification) to go from on-premise ADFS to Azure ADFS. After many emails with our IT department (who handles the Active Directory) we finally managed to update the Assertion Attributes Mapping with our application.
Everything was working fine with the plugin on the on-premise ADFS app. Since we've updated with the Azure ADFS there's a new error : [EDIT] : Error message is : username X has already been taken. email X has already been taken
It seems like the plugin try to save the User before trying to log in ? Now if I delete the user in craft it re-create it just fine then login. If I logout then try to log in again the error will trigger.
Here is my composer.json and composer.lock
I've tried version 2.1.2, 2.1.7, 2.1.12
Any idea what is going on ?