000031023 - AAH-KBA in UAT is not working using Ruleset = public.testing.redherrings

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 Number000031023
Applies ToRSA Product Set: Adaptive Authentication (Hosted)
RSA Product/Service Type: Adaptive Authentication (Hosted)
RSA Version/Condition: 11
Platform: KBA method in UAT
 
IssueA customer may say that  KBA authenticaton is not working in their UAT, they may report errors being returned. 
Tasks1. Information Gathering:
  • What is the FI in UAT?
  • Provide the RULE SET that is being used in the UAT FI. 
  • You may need to ask for the latest Loadsheet that was put into UAT FI.
  • Ask what are the users that are being used and what errors are being returned.
ResolutionFor testing, Lexis-Nexis provides our customers with a special rule set called
public.testing.redherrings
With this rule set are specific userids provided for testing that allows for repeated attempts for same userid without being blocked.

A typical error seen is  ERROR</kbaResult><additionalInfo><errorCode>20565</errorCode><errorDescription>Based on the information provided, the individual could not be located. 
This message means that the format is getting to Lexis-Nexis, and being searched in the database, but there is no entry for the data elements presented. 
If this is the case, then the customer may be using real users that are not in the special limited database Lexis-Nexis has set up for the public.testing.redherrings  KBA Ruleset.

 
NotesAs an alternative to public.testing.redherring KBA ruleset, the customer can load the default rule set configured in UAT that is using live, real users that going to Lexis-Nexis.  However, to avoid them being blocked, from overly frequent use, they must put a 'tag' for testing. 

Attachments

    Outcomes