85 search results

…C) At this point, you will not be using *any* user provider inside of your authenticator. You'll simply be using the Ldap and EntityManager objects directly. Nice and simple. D) You will now only want *one* user provider in security.yml, and it will…
weaverryan
weaverryan
Read Full Comment
…method). I understand now correctly the distingo between the role of the "User Provider" for refreshing and passing the user at the beginning of each request and the effective injection of an other "ldap user provider" used for convenience later on... Without the ChainProvider existence…
Paul-André Duchesne
Paul-André Duchesne
Read Full Comment
LDAP, anything. Basically, the user can then *choose* how to log in. But ultimately, in your code when you call `$this->getUser()`, you don't care *how* they logged in (e.g. LDAP) - you just care who they are. > Also i discovered that when…
weaverryan
weaverryan
Read Full Comment
…actually* overlap and be re-usable. So, you probably *will* have some duplication here - it's just the nature of deciding access on one object vs querying for a list of objects from a database (or ldap). Now, to your situation :). A few points: A…
weaverryan
weaverryan
Read Full Comment
…and if it succeed, I return true. * if a user is not authenticated against the AD, I try to find him/her in the AD with the loadUserByUsername method of the ldap client. If (s)he's found, I return false meaning the username was…
Paul-André Duchesne
Paul-André Duchesne
Read Full Comment