Business Continuity Option and Fixed Passcodes

[ToddFaber]

We have turned on the Business Continuity Option license, giving us an extra 500 seat licenses for sixty days. Our normal seat license count is 1150, so we have 1650 with the BCO turned on. Once the sixty days is over and the seat license count drops back down to 1150, how does connectivity work? Will the first 1150 people to connect be allowed to connect and the person that is number 1151 trying to connect will be denied or will all users be stopped from connecting? We have set all the temporary users up to use a fixed passcode instead of assigning them a software token, for obvious reasons. Once we're through the corona thing, the temporary users will have their fixed passcodes removed. Which leads me to another question....is there an easy way to remove the fixed passcodes or do they have to be handled one by one? With token users, we can go to the Assigned SecurID Token page, select the tokens we want to unassign, and unassign them en masse. I haven't been able to find a way that displays all the users that have a fixed passcode, other than running a report.

Thanks, Todd

[JayGuillette · Accepted solution]

When you exceed your active User license count, like when BCO 1650 expires, users all still authenticate but you cannot assign any new user tokens until you get the active user count below your normal 1150.  You are hamstrung administratively, not in authtication. 

[ToddFaber]

Thanks for the info Jay. So I am understanding correctly, everybody that was given access to connect remotely, they would all still be able to connect. If 1650 were given the capability, 1650 would still be able to connect.

[TedBarbour]

Hi Todd - that is correct.  Also you can re-enable the BCO license up to 6 times.

I don't know your situation but I would recommend looking into also getting ODA (on-demand authentication) license to go along with your BCO so that you are not just using single factor fixed passcodes.

Hope that helps,

Ted