Cisco Bug: CSCun73604 - Secure Mobility (MUS) username doesn't follow domain\user@realm format
Jan 27, 2017
- Cisco Web Security Appliance
Known Affected Releases
Symptom: 1. If access policy is created based on domain\user, it won't match with the Remote identity for the user, however it will match with the Local identity for the same user. 2. When generating Web Tracking reports: - If user@realm is entered, only Remote logs will be shown. - If domain\user@relam is entered, only Local logs will be shown. - If user is entered, a page is presented and one of the two formats above must be chosen. and so two separate reports have to be run. Conditions: Secure Mobility is enabled. User identification through ASA is chosen. Remote identity is created, and transparent authentication through ASA is chosen. Access policy is created based on username (as opposed to AD group), one using the Local identity, and another using the Remote identity.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases