Users see "Error Retrieving Contact Information" Warning log shows "The settings property kba was not found"

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • SecureAuth version affected: All

    When attempting to login, Users see the error "Error Retrieving Contact information"



    Checking the D:\SecureAuth\SecureAuthxx\ErrorLog\Warning.log for the realm reveals the following message

    "ContextUser.GetUser: GetProfileProperties() exception:The settings property 'kba2' was not found."

    A defect means that when switching from "No Data Store" to "Active Directory" datastore, some required entries are missing from the Web.config


    Although it is possible to add the entries in manually, the safest option is to 

    1. Open the Web Admin Console

    2. Click Tools | Update Web Config

    3. Click Update

    This will go through your realms and add in any missing entries. 

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products

    1 out of 1 found this helpful


    1 comment
    • This defect affects the latest hotfix for 20.06 as well. It seems to cause an interesting scenario where saving the realm configuration from the data tab and allowing it to be "auto-encrypted" will remove the KBA1-3 values back out of the configuration.

      Is there a timeline on a fix?

      Comment actions Permalink

    Please sign in to leave a comment.