Skip to content

Commit

Permalink
Update identity-proofing-testing.md (#564)
Browse files Browse the repository at this point in the history
* Update identity-proofing-testing.md

* Update identity-proofing-testing.md

* Update _articles/identity-proofing-testing.md

Co-authored-by: Zach Margolis <[email protected]>

* Update _articles/identity-proofing-testing.md

Co-authored-by: Zach Margolis <[email protected]>

---------

Co-authored-by: Zach Margolis <[email protected]>
  • Loading branch information
benjaminchait and zachmargolis authored Jun 4, 2024
1 parent 49db123 commit acc504e
Showing 1 changed file with 22 additions and 5 deletions.
27 changes: 22 additions & 5 deletions _articles/identity-proofing-testing.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,26 @@
---
title: Identity Proofing Testing
description: >
Tips and tricks for testing identity proofing (IAL2 accounts) including
example fake phone numbers and example PII
Tips and tricks for testing identity verification ("proofing")
category: "AppDev"
subcategory: "Development"
layout: article
---

## Choose your environment

We operate a number of different environments, and testing behavior is different in our lower environments (such as `int` or `dev`).

You can use a [sample partner application]({% link _articles/appdev-cloud-gov-deploy.md %}) to start an identity-verified authentication.

Remember that `prod` and `staging` are typically hitting real vendors; but other environments typically use our "mock proofers" which simulate different experiences.

## Choose your verification level

At the sample application, you need to choose a "Level of Service" which simulates the different request types that a partner agency might send to Login.gov:
* **Identity-verified** is our legacy identity proofing experience, which does not require a biometric comparison.
* **Biometric Comparison** is our new identity proofing experience, which either requires a **remote biometric** or requires that the user completes **in-person proofing**.

## Gmail Extra Emails Trick

Currently an account can only be verified once. When testing in lower environments, we
Expand All @@ -32,17 +45,21 @@ And as an easy way to keep track of the emails, consider date-stamping them:
[gmail-trick]: https://gmail.googleblog.com/2008/03/2-hidden-ways-to-get-more-from-your.html

## Pass a YML for images
## Pass a YML for images (in `int` and `dev`)

Instead of uploading images of IDs (since we aren't supposed to have PII in sandbox environments),
you can upload a [specially-formatted YML file](https://developers.login.gov/testing/#data-testing).

## Sample SSN
## Sample SSN (in `int` and `dev`)

Our developer docs have [sample SSNs](https://developers.login.gov/testing/#personal-information-verification)
to get desired behavior.

## Sample Phone Numbers
## Simulate fraud tooling (in `int` and `dev`)

See [Device profiling and fraud detection]({% link _articles/device-profiling.md %}) for testing details.

## Sample Phone Numbers (in `int` and `dev`)

We also have [sample phone numbers](https://developers.login.gov/testing/#phone-number-verification)
to generate various proofing responses.

0 comments on commit acc504e

Please sign in to comment.