000026962 - How do I add new Authentication Methods to my organization(FI)? - RSA Adaptive Authentication (Hosted)

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000026962
Applies ToRSA Adaptive Authentication (Hosted)
For OOB Phone, OOB SMS or KBA authentiation methods, these are third party methods, and after implementation, to add these methods requires an engagement with Professional Services as Billable SOW(Statement of Work) Project.
The fine details of how end-users will be enrolled would be determined with the Professional Services Engineer, but in general it involves a period when collection of user information will occur that will be used for the authentication.
Usually Challenge Questions method remains active in the Financial Institution (FI) organization and the other methods are secondary, but this order can be reversed.
OOB Phone and OOB SMS are separate authentication methods, and if switching to OOB SMS form OOB Phone, a new Collection will have to occur for the end-users.
The impact on end-users can vary and Professional Service can work to explain the impact, and tailor it somewhat to your needs by scheduling the Collection in various ways.

If your organization wishes to engage PS for changes to Authentication methods, start out with a Case to Customer Support and indicate what you want to do, and you are willing to engage with Professional Services in a SOW if required.    

CS will take care of contacting Professional Services to get the project started.

IssueChallenge Questions is the usual default method that is configured through FI Loads, and require no further work to setup during implementation.    Other Authentication Methods may be set up at initial implementation but how does an organization add new Authentications after launch?
Legacy Article IDa65780

Attachments

    Outcomes