Known issues

  • For TOKENPUSH and SMARTCREDENTIALPUSH use-cases, if the user does not act on the push notification received on their Entrust application, the input required page will keep attempting to complete the transaction.

Known limitations

  • The adapter supports resource rules with an authentication decision of Skip Password for first factor for low risk cases.
  • When using the PingFederate authentication API and a user completes a TOKENPUSH or SMARTCREDENTIALPUSH authenticator, the user is taken to the INPUT_REQUIRED state. The user can submit the default template to continue and finish the flow.