Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Posting as I couldn't find documentation as to why this was happening. I am sure I couldn't find the correct documentation or thread due to use error and/or lack of coffee.I was hitting an issue with the SSP portal login. I was given the correct CCO ...
I have opened a support case for this issue, but i am interested to see if anyone experienced the same issues.I am running a cloud hosted deployment, controllers are on code version 20.9.5.3.For some reason users who have not logged in to the vManage...
Update and "resolution"Cisco TAC verified that I was not losing my mind and that there is a defect after they were able to replicate the issue. It seems that even when the "Inactive days before locked out" setting is disabled in the vManage>Administr...
This is happening in my Testing and Production deployment and both of the deployments are hosted. So I am fairly confident that this isn't just a one off situation.
Quick update on some of the inconsistencies found while digging as well as a quick "band-aid" for this "shadow account lock". Impacted user accounts have "last login" dates of 60-90+ days, but we can't exactly pin point the threshold before it locks....
Fun update:Based on what I am reading, netadmin users have the privilege level needed to unlock accounts that become locked. All of the accounts having issues for me were showing status active, so we attempted to use the unlock action to see if it fi...
That does sound similar to what we are seeing. Only difference is that the vManage isn't reporting the user as disabled inactive state. So when the "reset locked user" action is taken, it doesn't clear the issue. The only way we have found to reset a...
