User ID mapping when switching between wired and wireless

[MikeC]

A lot of my users login into their computers using the wired connection. Then when they are off to meetings, they switch to wireless (without logging out and logging back in).  If I turn off client probing, this creates an issue where they switch to wireless, as the ID never seems to map.  Is there a way to correct this?

FYI....network bridging is disabled currently, so when they are wired, their wireless connection is automatically disabled

[Remo · Accepted solution]

Do they authenticate in your wireless with their company credentials maybe with the authentication happening on a radius server? If yes, then use these logs for User-ID mapping.

If thats not the case then you need to make sure that you configure enough sources for user-ID like active-directory, exchange ... to make sure that the time without mappkng is as short as possible.

[MikeC]

---

@Remo wrote:

Do they authenticate in your wireless with their company credentials maybe with the authentication happening on a radius server? If yes, then use these logs for User-ID mapping.

If thats not the case then you need to make sure that you configure enough sources for user-ID like active-directory, exchange ... to make sure that the time without mappkng is as short as possible.

---

Yes! That's what I was just thinking. I'm using Cisco ACS for Radius auth. Is it pretty straight forward?

[BPry]

@MikeC,

THIS document should help you get the Syslog setup to send to the PA, and walk you through the User-ID side of things. 

[MikeC]

Thank you both!