User-ID - issues with mapping from Juniper Mist wireless

[ParticularNoobie]

Hello. 

I have issues with mapping user from Juniper Mist. User-ID is set and working fine when monitoring LAN traffic. But when I want to check wireless users I don't see Source User. From my research I understand I need some type of "bridge" between Juniper Mist and Panorama in form on syslog. 
Sadly both systems are supported by separate companies so I cant ask them for help in this case. 

Do anyone here have similar issue in past with Juniper Mist and Panorama? And give me any clue where I need to dig for information? Or which syslog (open source will be best) I can use as "bridge" between those two systems?

Thank you for any advices

[BPry]

@ParticularNoobie,

How are you authenticating users on the Juniper side of things? If you're using RADIUS for authentication you could just pull logs from your RADIUS server(s) directly. It's possible that you don't actually need to utilize SYSLOG scrapping depending on your authentication setup.

If you do require syslog scrapping you don't actually need to have any sort of intermediate solution. You can send SYSLOG directly to Panorama with additional information available HERE. You can also use an intermediate solution like Graylog as an open-source example that you can then have configured to update user mappings through the API easily as well. If you don't already have that setup just enabling the firewall as a listener is a more straight-forward solution however.

[ParticularNoobie]

Thank you for response BPry.
Both systems pulling info from this same Radius. That (with my knowledge) its strange. Juniper auth users by Windows AD (Radius) I can log into server and check users IP/Username for wifi. LAN users using this same Windows AD (Radius) for access desktops (docked laptops). And also I can of course log into this same server and check second vlan and see IP/Username of those users.

But Panorama showing only LAN users, and ignoring all Juniper/Wifi users. 

Idea about syslog server was put in my head after conversation (with many long mails with screenshots and few life session when I explaining what is where or exactly what is missing) with our PaloAlto support as "only solution". 

I hope that will bring more light on this case.