Unable to authenticate against the Symantec’s Validation and ID Protection Enterprise Gateway when using the Microsoft Credential Provider plug in
search cancel

Unable to authenticate against the Symantec’s Validation and ID Protection Enterprise Gateway when using the Microsoft Credential Provider plug in

book

Article ID: 164519

calendar_today

Updated On:

Products

VIP Service

Issue/Introduction

Logging into a server with the VIP Microsoft Credential Provider plugin installed returns an access denied error message when using LDAP Password + Security Code when prompted at the Microsoft Credential Provider login.

Cause

The Microsoft Credential Provider plugin supports UO (User Name + Security Code) validation server. This error occurs when the validation server set to User Name + LDAP Password + Security code.

Resolution

To resolve this issue, please follow the steps below to create a new UO validation server for the MCP integration:
 

  1. Log into your Enterprise Gateway.
  2. Click on Validation tab.
  3. Stop your current Validation Server you are using for the Microsoft Credential Provider plug in validation.
  4. Click Add Server and select Microsoft > Credential Provider template.
  5. Select “User ID – Security Code” as the Validation Mode.
  6. Enter a Server Name.
  7. Enter the port number the Validation Server should listen on (this can be the same port as the non-working validation server)
  8. Enter the Radius Shared Secret (non-encrypted).
  9. Click Submit and confirm the Server is started.
  10. Try validations again.
  11. Delete the non-working Validation Server.