Phone number updates to 2FA Starling are not being processed in a timely manner (4295757)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Phone number updates to 2FA Starling are not being processed in a timely manner
Description

In CAM we have an Authenticator defined that looks for the 'mobile' field in AD to request a token via 2FA Starling.
If we create a new user in AD allowed to logon to CAM with that mobile field populated with a valid phone number - it works
If we update that mobile field in AD, with a different phone number, it can take up to an hour before Defender as a Service starts sending tokens to the new number. In the meantime it sends to the 'old' phone number
Cause

CAM caches the phone number value which expires after 60 minutes
Resolution

WORKAROUND:
Restart the Dell Redist. Secure Token Server service to clear the cache which can cause a short outage
STATUS:
Enhancement Request 676860 - Change the lifetime of phone number cache for 2FA has been submitted to the Development Team for consideration in a future release of CAM.
Defect ID

676860

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title