Impact attributes modifications in ORM about fr3dldapbundle HOT 8 CLOSED

You can choose between 2 options. Users managed by FOS or managed by LDAP Directory.

If you're not using FOS for user management (Roles, etc) then remove it from the user provider chain so always the user is retrieved from the LDAP Directory.

from fr3dldapbundle.

Sorry for my poor english. This is not the problem I adressed : While using LDAP authetication, user fields are correctly initiated depending on the mapping defined in the configuration but, il the mapped user's LDAPs attributes change afterwards, the fields are not updated when the users connects again.

from fr3dldapbundle.

Yea I understand that part. If you don't need FOSUserBundle you can remove it from the "user provider" and always the user data will be retrieved from the LDAP Directory in each login.

from fr3dldapbundle.

Do you mean that if FOS is activated, users are created in fos at the first login and this is the reason why mapped attributes are not updated any more ?

from fr3dldapbundle.

User data is retrieved from the first user provider present in the user provider chain. If FOS is the first then the data is retrieved from the BD, if not user is present in FOS then SF will check for the next user provider (fr3d_user_provider) and the data will be retrieved from the LDAP.

from fr3dldapbundle.

I understand but when I use fr3dldapbundle before fosuser in the provider chain, the first login with an LDAP account is OK and the second fails because the plugin creates a new user object that cannot be persisted because it already exists whith the username. so that i still need the same hack

from fr3dldapbundle.

Sorry but is out of the scope of this bundle copy ldap attributes with database attributes. Instead you merge the fields that you want making a function listening the login event.

from fr3dldapbundle.

Finally, you shouldn't need patch LdapManager, just extending it in your own bundle and setup the new manager to use in the ldap config

from fr3dldapbundle.