problems with device manager tacacs authentication
We've recently upgraded our Device Manager to 4.1(3a) and have a mix of switches running this version as well as older versions (3.3(3)). We use AAA tacacs+ on the switches to a Cisco ACS server for user authentication. The ACS server backends out to our Windows Domain authentication service. Typically usernames are formatted as follows: domain\username
This has worked fine for a long time, however now DM 4.1(3a) can't authenticate a user on a 3.3(3) switch. Various debugs and logs on the ACS point to problems handling the \ character in the username. A single \ gets "eaten" by either DM or the switch(don't know which) and the ACS sees a login attempt from domainusername, which of course fails. A \\ doesn't work either, in this case both \ characters are passed through to the ACS which now see a login attempt from domain\\username which also fails.
Looked at all the release notes, CCO bug searches, google and previous forum articles and found nothing on this.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...