--- title: PingOne Verify Evaluation node description: The PingOne Verify Evaluation node uses the PingOne Verify Service to initiate a new or continue an existing verification transaction. component: auth-node-ref version: latest page_id: auth-node-ref:pingone:pingone-verify-evaluation canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/pingone/pingone-verify-evaluation.html page_aliases: ["auth-node-pingone-verify-evaluation.adoc"] superseded_by: https://docs.pingidentity.com/auth-node-ref/latest/pingone/pingone-verify-evaluation.html section_ids: example: Example availability: Availability inputs: Inputs dependencies: Dependencies configuration: Configuration outputs: Outputs callbacks: Callbacks outcomes: Outcomes pingone_verify_eval_node_errors: Errors --- # PingOne Verify Evaluation node The PingOne Verify Evaluation node uses the PingOne Verify Service to initiate a new or continue an existing verification transaction. It offers a range of delivery methods, such as a QR code, email, or SMS to start the identity verification process. You can customize the verification types end users can perform in your PingOne [Verify policy](https://docs.pingidentity.com/pingone/identity_verification_using_pingone_verify/p1_verify_policies.html). ## Example The following example journey integrates PingOne Verify to perform user identity verification. ![Example PingOne Verify journey](_images/pingone-verify-example-journey-full.png)Figure 1. Example PingOne Verify journey * The user enters their credentials and the [Data Store Decision node](../data-store-decision.html) matches them against the identity store. * a The [PingOne Identity Match node](pingone-identity-match.html) checks PingOne for a matching user. * b If a user is found, the [PingOne Verify Completion Decision node](pingone-verify-completion-decision.html) checks the user's most recent verification transaction to determine the status: * Success The user successfully completed the most recent PingOne Verify transaction, so the journey progresses directly to the Success node and authentication is successful. * Not Completed The user has an existing PingOne Verify transaction in progress, so the journey resumes the existing verification transaction. The node adds the user's existing transaction ID to the shared node state in a variable named `pingOneVerifyTransactionId`. * Not Started / Failure / Expired * The user doesn't have an existing PingOne Verify transaction (`Not Started`) * The user hasn't successfully completed the most recent PingOne Verify transaction * The most recent PingOne Verify transaction has expired The journey continues to start a new verification transaction. * c If no matching user is found, the [PingOne Create User node](pingone-create-user.html) creates a new user in PingOne. * d The [PingOne Verify Evaluation node](pingone-verify-evaluation.html) starts a new PingOne Verify evaluation or continues an existing evaluation if `pingOneVerifyTransactionId` is present in the shared node state. The node either completes or fails the journey based on the result. ## Availability | Product | Available? | | ------------------------------------- | ---------- | | PingOne Advanced Identity Cloud | Yes | | PingAM (self-managed) | Yes | | Ping Identity Platform (self-managed) | Yes | ## Inputs * This node requires the end user to have an account in the PingOne environment. The node reads the PingOne user ID for that account in a shared state variable named `pingOneUserId`. Use a [PingOne Identity Match node](pingone-identity-match.html) to populate the shared state with the user's PingOne ID. * If there's a transaction ID in the shared state variable named `pingOneVerifyTransactionId`, this node continues that in-progress evaluation, rather than starting a new one. Use a [PingOne Verify Completion Decision node](pingone-verify-completion-decision.html) to determine the status of any previous transactions and populate the shared state with an in-progress transaction ID. ## Dependencies This node requires a PingOne Worker Service configuration so that it can connect to your PingOne instance and send it the necessary data to perform PingOne Verify evaluations as part of the journey. Find more information in [Set up PingOne workers and configure them as Advanced Identity Cloud services](https://docs.pingidentity.com/pingoneaic/integrations/pingone-set-up-workers.html). ## Configuration | Property | Usage | | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | PingOne Worker service ID | The ID of the PingOne worker service for connecting to PingOne. | | Verify policy ID | The ID of the policy to use for the PingOne Verify evaluation.If not specified, the node uses the environment's default Verify policy. | | Verify URL delivery method | How the user will receive the URL they need to start a PingOne Verify evaluation.Choose from:- `QR code` Display the URL as a QR code. - `Email` Send an email containing the URL to the email address in the user's Advanced Identity Cloud identity profile. - `SMS` Send an SMS containing the URL to the phone number in the user's Advanced Identity Cloud identity profile. - `Redirect` Redirect the user to the PingOne Verify web app for identity verification.On completion, redirect the user back to Advanced Identity Cloud to continue the authentication journey.Default: `QR Code` | | Allow same device verification | When enabled, the node presents the user with an option to continue the identity verification process on their current device. This property only displays if Verify URL delivery method is set to QR code. | | Allow user to choose the URL delivery method | When enabled, the node prompts the user to choose the URL delivery method. | | Automatic redirect | If the Verify URL delivery method is `Redirect`, enable this option to automatically redirect the end user back to the journey after successfully completing the verification process in PingOne Verify.Default: Not enabled. The end user *must* click the Return button within the journey timeout period to be redirected back to the journey. | | Hide verification code | When enabled, suppress the display of the verification code in the PingOne Verify web UI. This setting applies to both the `QR code` and `Redirect` delivery methods.Default: Not enabled. The verification code is displayed in the PingOne Verify web UI. | | Delivery method message | Add the text per locale to display when prompting the user to choose their delivery method:1) Click Add. 2) In the Key field, enter the locale.[(1)](#message-locale-footnote-verify) If the incoming HTTP request doesn't include the header or the preferred locales don't match any configured locales, the node uses the first text in the list. 3) In the Value field, enter the text to display to the user. If you leave this blank, the node displays a localized version of the following text: `Select the delivery method to start the identity verification process.`To edit an entry, click its pencil icon ([icon: pencil-alt, set=fa]).To remove an entry, click its delete icon ([icon: trash, set=fa]). | | QR code message | Add the text per locale to display when you select QR code as the delivery method:1) Click Add. 2) In the Key field, enter the locale.[(1)](#message-locale-footnote-verify) If the incoming HTTP request doesn't include the header or the preferred locales don't match any configured locales, the node uses the first text in the list. 3) In the Value field, enter the text to display to the user. If you leave this blank, the node displays a localized version of the following text: `Scan the QR code to initiate the identity verification process.`To edit an entry, click its pencil icon ([icon: pencil-alt, set=fa]).To remove an entry, click its delete icon ([icon: trash, set=fa]). | | Waiting message | Add the text per locale to display while waiting for the user to respond to the Verify transaction, when using the SMS or Email delivery methods:1) Click Add. 2) In the Key field, enter the locale.[(1)](#message-locale-footnote-verify) If the incoming HTTP request doesn't include the header or the preferred locales don't match any configured locales, the node uses the first text in the list. 3) In the Value field, enter the text to display to the user. You can use the following variable in the `Value` field: * `{{verificationCode}}` A 6-digit code that the user can match against the code displayed when they begin verification. For example, `981092`. ![pingone verify verification code](_images/pingone-verify-verification-code.png)Figure 2. Compare the code displayed on screen with the code presented during verification. If you leave this blank, the node displays a localized version of the following text: `Waiting for identity verification completion. Here is the code you will see on your device: {{verificationCode}}`To edit an entry, click its pencil icon ([icon: pencil-alt, set=fa]).To remove an entry, click its delete icon ([icon: trash, set=fa]). | | Redirect message | Add the text per locale to display when you select Redirect as the delivery method, and the node redirects the user back to Advanced Identity Cloud to continue the journey:1) Click Add. 2) In the Key field, enter the locale.[(1)](#message-locale-footnote-verify) If the incoming HTTP request doesn't include the header or the preferred locales don't match any configured locales, the node uses the first text in the list. 3) In the Value field, enter the text to display to the user.To edit an entry, click its pencil icon ([icon: pencil-alt, set=fa]).To remove an entry, click its delete icon ([icon: trash, set=fa]). You can't set a message here if you've enabled Automatic redirect. | | Verify transaction timeout | The period of time (in seconds) to wait for a response to the Verify transaction. If no response is received during this time, the node times out and the verification process fails.Default: `120` seconds | | User profile biographic matching | Attributes from the user profile to compare with the data extracted from the user's government identity document.If no attributes are listed here, no user profile biographic matching verification is performed.To create a pairing:1) Click Add. 2) In the Key field, enter the biographic matching requirement. One of: * `referenceSelfie` The photo the user took of themselves, in base64-encoded data form. * `phone` The phone number obtained from the user's identification. * `email` The email address obtained from the user's identification. * `given_name` The first, or given name obtained from the user's identification. For example, `Babs`. * `family_name` The last, surname, or family name obtained from the user's identification. For example, `Jensen`. * `name` The full name obtained from the user's identification. For example, `Babs Jensen`. * `address` The address obtained from the user's identification, as a single string. For example, `123 Any Street, London, United Kingdom, CH15 1EE`. * `birth_date` The date of birth obtained from the user's identification. 3) In the Value field, enter the attribute in the user's Advanced Identity Cloud profile that should match. For example, you could pair the `family_name` biographic key to the `sn` profile attribute.To edit an entry, click its pencil icon ([icon: pencil-alt, set=fa]).To remove an entry, click its delete icon ([icon: trash, set=fa]). Keys must be unique across user profile biographic matching and node state biographic matching. | | Node state biographic matching | Attributes from the node state to compare with the data extracted from the user's government identity document.You can set these attributes in the node state using a [Scripted Decision node](../scripted-decision.html) before this node in the journey.If no attributes are listed here, no node state biographic matching verification is performed.To create a pairing:1) Click Add. 2) In the Key field, enter the biographic matching requirement. One of: * `referenceSelfie` The photo the user took of themselves, in base64-encoded data form. * `phone` The phone number obtained from the user's identification. * `email` The email address obtained from the user's identification. * `given_name` The first, or given name obtained from the user's identification. For example, `Babs`. * `family_name` The last, surname, or family name obtained from the user's identification. For example, `Jensen`. * `name` The full name obtained from the user's identification. For example, `Babs Jensen`. * `address` The address obtained from the user's identification, as a single string. For example, `123 Any Street, London, United Kingdom, CH15 1EE`. * `birth_date` The date of birth obtained from the user's identification. 3) In the Value field, enter the attribute in the node state that should match. For example, you could pair the `family_name` biographic key to `sn` in the node state.To edit an entry, click its pencil icon ([icon: pencil-alt, set=fa]).To remove an entry, click its delete icon ([icon: trash, set=fa]). Keys must be unique across user profile biographic matching and node state biographic matching. | | Store verification metadata | When enabled, store the verification metadata returned from PingOne Verify in shared state under a key named `pingOneVerifyMetadata`.> **Collapse: Example verification metadata** > > ```json > { > "_links":{ > "environment":{ > "href":"https://api.pingone.eu/v1/environments/environment-id" > }, > "verifyTransaction":{ > "href":"https://api.pingone.eu/v1/environments/environment-id/users/username/verifyTransactions/transaction-id" > }, > "self":{ > "href":"https://api.pingone.eu/v1/environments/environment-id/users/username/verifyTransactions/transaction-id/metaData" > }, > "user":{ > "href":"https://api.pingone.eu/v1/environments/environment-id/users/username" > } > }, > "_embedded":{ > "metaData":[ > { > "_links":{ > "self":{ > "href":"https://api.pingone.eu/v1/environments/environment-id/users/username/verifyTransactions/transaction-id/metaData/23fd5f41-cadf-4478-baf7-6860ede3fb7f" > } > }, > "id":"23fd5f41-cadf-4478-baf7-6860ede3fb7f", > "provider":"IDRND", > "type":"INJECTION_DETECTION", > "status":"SUCCESS", > "data":{ > "probability":1.0 > }, > "retry":{ > "attempt":1 > } > }, > { > "_links":{ > "self":{ > "href":"https://api.pingone.eu/v1/environments/environment-id/users/username/verifyTransactions/transaction-id/metaData/30327d17-0b16-42a6-af4a-84028a6cdcbb" > } > }, > "id":"30327d17-0b16-42a6-af4a-84028a6cdcbb", > "provider":"MITEK", > "type":"DOCUMENT_AUTHENTICATION", > "status":"SUCCESS", > "data":{ > "mitekVerifications":[ > { > "name":"Document Ensemble Authenticator", > "judgement":"Authentic", > "verificationType":202, > "probability":978, > "version":"4.5.0.3853", > "documentId":"1b9bb5a7-8ecc-452c-b27b-540011748f05" > }, > { > "name":"Black And White Copy", > "judgement":"Authentic", > "verificationType":102, > "probability":670, > "version":"4.5.0.3853", > "documentId":"e32f88c6-f59d-4d38-9399-813d8416a991" > }, > { > "name":"Ensemble Authenticator", > "judgement":"Authentic", > "verificationType":201, > "probability":978, > "version":"4.5.0.3853", > "documentId":"e32f88c6-f59d-4d38-9399-813d8416a991" > }, > { > "name":"Human Face Presence", > "judgement":"Authentic", > "verificationType":300, > "probability":1000, > "version":"4.5.0.3853", > "documentId":"e32f88c6-f59d-4d38-9399-813d8416a991" > }, > { > "name":"ID Document Blacklist", > "judgement":"Authentic", > "verificationType":101, > "probability":1000, > "version":"4.5.0.3853", > "documentId":"e32f88c6-f59d-4d38-9399-813d8416a991" > }, > { > "name":"Generic Font", > "judgement":"Authentic", > "verificationType":104, > "probability":940, > "version":"4.5.0.3853", > "documentId":"e32f88c6-f59d-4d38-9399-813d8416a991" > }, > { > "name":"Rounded Corner Presence", > "judgement":"Authentic", > "verificationType":100, > "probability":995, > "version":"4.5.0.3853", > "documentId":"e32f88c6-f59d-4d38-9399-813d8416a991" > }, > { > "name":"Image Processing", > "judgement":"Authentic", > "verificationType":710, > "probability":1000, > "version":"1.0", > "documentId":"e32f88c6-f59d-4d38-9399-813d8416a991" > }, > { > "name":"Document Liveness", > "judgement":"Authentic", > "verificationType":108, > "probability":963, > "version":"2.2", > "documentId":"e32f88c6-f59d-4d38-9399-813d8416a991" > }, > { > "name":"Portrait Substitution", > "judgement":"Authentic", > "verificationType":305, > "probability":994, > "version":"2.2", > "documentId":"e32f88c6-f59d-4d38-9399-813d8416a991" > } > ], > "frontImageDocumentId":"e32f88c6-f59d-4d38-9399-813d8416a991", > "documentEvidenceId":"1b9bb5a7-8ecc-452c-b27b-540011748f05" > } > }, > { > "_links":{ > "self":{ > "href":"https://api.pingone.eu/v1/environments/environment-id/users/username/verifyTransactions/transaction-id/metaData/e4b093cc-80f1-4d3b-929e-4f9708b7ea22" > } > }, > "id":"e4b093cc-80f1-4d3b-929e-4f9708b7ea22", > "provider":"AMAZON", > "type":"FACIAL_COMPARISON", > "status":"SUCCESS", > "data":{ > "similarity":99.78133, > "confidence":99.99536, > "quality":{ > "brightness":84.50669, > "sharpness":38.89601 > } > } > }, > { > "_links":{ > "self":{ > "href":"https://api.pingone.eu/v1/environments/environment-id/users/username/verifyTransactions/transaction-id/metaData/6b149c53-86b8-490b-9916-a13d27b0a5ed" > } > }, > "id":"6b149c53-86b8-490b-9916-a13d27b0a5ed", > "provider":"IDRND", > "type":"LIVENESS", > "status":"SUCCESS", > "data":{ > "score":1.012497, > "probability":0.7335085, > "quality":0.976563 > }, > "retry":{ > "attempt":1 > } > }, > { > "_links":{ > "self":{ > "href":"https://api.pingone.eu/v1/environments/environment-id/users/username/verifyTransactions/transaction-id/metaData/2cbf7b6a-0ecc-4979-a9fc-7289a9179123" > } > }, > "id":"2cbf7b6a-0ecc-4979-a9fc-7289a9179123", > "provider":"AMAZON", > "type":"FACIAL_COMPARISON_REFERENCE_SELFIE", > "status":"SUCCESS", > "data":{ > "comparisons":[ > { > "source":"SELFIE", > "target":"REQUIREMENTS", > "status":"SUCCESS", > "detailedResults":{ > "similarity":99.75465, > "confidence":99.998604, > "quality":{ > "brightness":96.05589, > "sharpness":99.66375 > } > } > } > ] > } > } > ] > }, > "size":5 > } > ``` If the node can't retrieve the verification metadata from PingOne, the pingOneVerifyMetadata key is empty. FACIAL\_COMPARISON\_REFERENCE\_SELFIE is a PingOne Verify metadata type that lets you distinguish between selfies and government IDs. Previously, both were tracked in the FACIAL\_COMPARISON metadata type. If you were using this type for reference selfies, adjust your scripts accordingly. Find more information in PingOne Verify types of verification.Default: Disabled | | Store verified data | When enabled, store a list of the verified data submitted by the user in shared state under a key named `pingOneVerifyVerifiedData`.> **Collapse: Example verified data** > > ```json > { > "_links":{ > "self":{ > "href":"https://api.pingone.com/v1/environments/environment-id/users/user-id/verifyTransactions/0e2ed48f-6c3a-46c4-bcb5-3a6bd791348b/verifiedData/34613a50-672c-428f-8db9-c67fe09fc4cc" > }, > "environment":{ > "href":"https://api.pingone.com/v1/environments/environment-id" > }, > "user":{ > "href":"https://api.pingone.com/v1/users/user-id" > }, > "transaction":{ > "href":"https://api.pingone.com/v1/environments/environment-id/users/user-id/verifyTransactions/0e2ed48f-6c3a-46c4-bcb5-3a6bd791348b" > } > }, > "id":"84170421-62c6-49a5-b343-496bee93c206", > "type":"GOVERNMENT_ID", > "createdAt":"2022-02-23T15:51:01.603Z", > "data":{ > "addressCity":"this city", > "addressState":"this state", > "addressZip":"11111", > "birthDate":"1970-01-01", > "country":"USA", > "expirationDate":"1970-01-01", > "firstName":"given", > "gender":"", > "idNumber":"11111", > "issueDate":"1970-01-01", > "issuingCountry":"", > "lastName":"surname", > "nationality":"", > "weight":"" > }, > "retry":{ > "attempt":1 > } > } > ``` If the node can't retrieve the verification metadata from PingOne, the pingOneVerifyMetadata key is empty.Default: Disabled | | Capture failure | Capture the details in shared state if a failure occurs.The node stores the details in a variable named `pingOneVerifyEvaluationFailureReason`.Learn more about the errors this node can return in [Errors](#pingone_verify_eval_node_errors).Default: `False` | (1) Specify a [locale that Java supports](https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/util/Locale.html), such as `en-gb`. Otherwise, the node throws a configuration exception with an `Invalid locale provided` message. ## Outputs * If you select Store Verification Metadata, the node outputs the verification metadata JSON in a state variable named `pingOneVerifyMetadata`. To learn more about verification metadata, refer to [Read All Verification Metadata](https://apidocs.pingidentity.com/pingone/platform/v1/api/#get-read-all-verification-metadata). * If you select Store Verified Data, the node outputs the verified information gathered from the user's ID in a state variable named `pingOneVerifyVerifiedData`. To learn more about verified data, refer to [Read One User Verified Data](https://apidocs.pingidentity.com/pingone/platform/v1/api/#get-read-one-user-verified-data). * If you select Capture failure, the node stores any error response in a shared state variable named `pingOneVerifyEvaluationFailureReason`. ## Callbacks * If Allow user to choose the URL delivery method is selected, the node sends the following callbacks: * `TextOutputCallback` Contains the Delivery method message. * `ConfirmationCallback` Contains the options available to the client application. * When using the `QR Code` URL delivery method, the node sends the following callbacks: * `TextOutputCallback` Contains the QR Code message. * `ScriptTextOutputCallback` Contains JavaScript script to run to display the QR code. * `HiddenValueCallback` Contains the actual URL to start the verification. The client might display this to users on a mobile device that can't scan a QR code, or to render their own QR code, for example. * `PollingWaitCallback` Waits for the user to complete the verification and contains the Waiting message. * When using the `Email` or `SMS` URL delivery method, the node sends the following callbacks: * `PollingWaitCallback` Waits for the user to complete the verification and contains the Waiting message. * When using the `Redirect` delivery method, the node sends the following callbacks: * `RedirectCallback` Contains the URI to redirect the user to for identity verification, using the PingOne Verify web application. Learn more in [Supported callbacks](https://docs.pingidentity.com/pingoneaic/am-authentication/callbacks-supported.html). ## Outcomes * `Success` The user successfully completed the PingOne Verify evaluation. * `Failure` The user did not successfully complete the PingOne Verify evaluation, or an error occurred. * `Time Out` The node did not receive a response from the user performing the verification before the timeout specified in the Verify Transaction Timeout property. ## Errors This node can output the errors in the following table. | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | | Enable **Capture failure** to store errors in shared state in a variable named `pingOneVerifyEvaluationFailureReason`.The node stores errors in this format:```json { "code": "{{Error code}}", "message": "{{Error message}}", "exception": "", } ``` | **PingOne Verify Evaluation node error codes and messages** | Error code | Error message | | ------------------------------------------- | ---------------------------------------------------------------- | | `ACCESS_TOKEN` | Unable to get access token for PingOne Worker. | | `IDENTITY_NOT_FOUND` | Could not find the identity with username in the realm. | | `INVALID_ATTRIBUTE_CONFIGURATION` | Could not get the value for the configured user attribute. | | `INVALID_BIOGRAPHIC_MATCHING` | Unexpected key value found in Biographic Matching. | | `IDENTITY_NOT_FOUND` | Could not find the identity with username in the realm. | | `IDENTITY_VERIFICATION_FAILED` | Identity verification failed. | | `JSON_PROCESSING_ERROR` | Error processing JSON data. | | `MISSING_ATTRIBUTE_FROM_PROFILE` | Could not get attribute from user profile. | | `MISSING_PINGONE_USER_ID_FROM_SHARED_STATE` | Expected PingOne User ID to be set in sharedState. | | `MISSING_PINGONE_VERIFY_TRANSACTION_ID` | Expected PingOne Verify Transaction ID to be set in sharedState. | | `MISSING_USERNAME` | Could not get the username from the context. | | `REDIRECT_FLOW_FAILED_CODE_MISMATCH` | Redirect flow failed. Code mismatch. | | `REDIRECT_FLOW_FAILED_MISSING_CODE` | Redirect flow failed. Code not found in request parameters. | | `UNEXPECTED_ERROR` | An unexpected error occurred. | | `UNEXPECTED_VERIFY_STATUS` | Unexpected status returned from PingOne Verify Transaction. | | | | | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | The PingOne Verify transaction API can return `INVALID_VALUE` as a validation error if a field in the request has an invalid or missing value. This isn't a PingOne Verify Evaluation node error code but can indicate that a value you're sending to PingOne Verify doesn't satisfy current PingOne Verify validation rules. |