Message Provider Configuration resets after 3.4 install/upgrade + temporary auth errors

Products

• VIP Authentication Hub

Issue/Introduction

After upgrading VIP AuthHub environment to 3.4, it was observed that the Twilio configuration had been changed to what appears some default. You had previously configured this via a patch request to /admin/v1/MessageProviders/twillio as described in the documentation. 

Issue can be easily recreated during a subsequent upgrade, as well as running a rollout restart. In all cases, the phone number and other values of the Twillio config were changed, confirmed via a GET request to /admin/v1/MessageProvider as well as OTP's being sent from a different phone number. On the final recreation of this issue, Authentication Errors from the OTP Generator were also experienced. The issue resolved itself after a few hours, however looking in the logs we do see exceptions thrown. During this time, no SMS OTPs could be sent, however email OTPs could be sent.

msg: Unable to send notifications: Authenticate
thread: SSP_COMMON_ASYNC_EXECUTOR4
throwable: com.broadcom.layer7authentication.mds.service.common.MdsException: Authenticate at com.broadcom.layer7authentication.mds.service.util.ExceptionUtil.getBadRequestException(ExceptionUtil.java:19) at com.broadcom.layer7authentication.mds.service.providers.sms.TwilioSmsService.sendNotification(TwilioSmsService.java:132) at com.broadcom.layer7authentication.mds.service.providers.sms.TwilioSmsService.sendMultiple(TwilioSmsService.java:211) at com.broadcom.layer7authentication.mds.service.providers.sms.TwilioSmsService.notifyUser(TwilioSmsService.java:185) at com.broadcom.layer7authentication.mds.service.impl.MessageDeliveryHandler.deliverMessages(MessageDeliveryHandler.java:103) at com.broadcom.layer7authentication.mds.service.MessageDeliveryService.lambda$sendAsync$0(MessageDeliveryService.java:81) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583)

Environment

VIP AuthHub

Release : 3.4.1

Resolution

This issue is identified as a bug and will be addressed as part of the next VIP Authentication Hub release. Please reach out to Broadcom Customer Care if any further information is required on this topic.