Connectors

November 2023

November 11

Updated Error Mappings

Fixed Flow Conductor Connector

The error mappings for the Flow Conductor Connector OOB Continue and OOB Start capabilities have been updated.

The following error mappings were removed from the OOB Continue capability:

'missingQueryData': 'The request did not include query data',

'missingTokenData': 'The request was missing token data',

'jwtError': 'There was a problem parsing the JWT',

'validationError': 'There was a problem validating the JWT contents',

'challengeRefExpired': 'The challenge reference has expired',

'challengeRefNotFound': 'The challenge reference was not found',

'challengeExpired': 'The challenge has expired',

'challengeNotFound': 'The challenge could not be found',

'challengeRefError': 'The challenge reference is invalid',

'challengeAlreadyApproved': 'The challenge has already been approved'

If you modified any of these error messages, the modified version will remain. You can delete and recreate the node to remove the older mapping.

The following error mappings were added to the OOB Start capability:

'challengeExpired': 'The challenge has expired',

'challengeAlreadyApproved': 'The challenge has already been approved',

'unexpectedError': 'An unexpected error occurred'

The OOB Start capacity also includes a non-customizable error message displayed for some backend issues: An internal error has occurred. Contact support if you see this error message or unexpectedError.

PingOne RADIUS Gateway flow enhancement

Improved PingOne RADIUS Gateway Connector

We’ve added the ability to evaluate PingID authentication policies to all RADIUS Gateway flows with the PingOne RADIUS Gateway Connector. To support this enhancement, we’ve also added the Policy Evaluation capability to the PingID Connector.

PingID authentication subflow enhancements

Improved PingID Connector

The PingID Connector authentication subflow now includes the following features:

  • We’ve added the ability to evaluate and apply PingID policy to the PingID sub-flows To support this enhancement, we’ve added the Policy Evaluation capability to the PingID connector.

  • Administrators can now define a list of mandatory authentication methods. If defined, users are forced to register all the required authentication methods to access their resources.

  • If a user does not have a registered device during an authentication flow, after they successfully register a new device they are also required to authenticate with the new device.