Hello All,
in the status page when you login there is no lookup::person called.
Try to apply this patch and let me know if it's ok.
```
diff --git
a/html/captive-portal/lib/captiveportal/PacketFence/Controller/Authenticate.pm
b/html/captive-portal/lib/captiveportal/PacketFence/Controller/Aut
Correction. Apparently this isn't the root cause.
Would really like to figure out why some users get their name and email
populated from AD and others don't.
On Fri, Jan 25, 2019 at 1:51 PM Christian McDonald
wrote:
> I think I can reliably reproduce this.
>
> It seems that these other user att
I think I can reliably reproduce this.
It seems that these other user attributes are only populated when a user
actually registers a device. The user simply logging into the /status page
creates the user account entry but doesn't populate the fields from AD.
On Fri, Jan 25, 2019 at 1:43 PM Murilo
These issues are often in my environment too, but it does not happen on all
users...
Em sex, 25 de jan de 2019 16:23, Christian McDonald via PacketFence-users <
packetfence-users@lists.sourceforge.net> escreveu:
> Hello,
>
> I have a fresh install of PF 8.3 on CentOS7. All I have done is bind to
Hello,
I have a fresh install of PF 8.3 on CentOS7. All I have done is bind to my
AD domain and created a internal AD authentication source. I can login to
the /status page on the portal and user accounts are created in
PacketFence. However, none of the attributes from AD are populating. I am
only
