Skip to content
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.

Backend - expose a verification endpoint #1062

Closed
adriaaaa opened this issue Aug 10, 2022 · 1 comment · Fixed by #1111
Closed

Backend - expose a verification endpoint #1062

adriaaaa opened this issue Aug 10, 2022 · 1 comment · Fixed by #1111
Assignees
@pattisdr
Labels
Subject Identity Verification

Comments

@adriaaaa
Copy link

adriaaaa commented Aug 10, 2022 •
edited
Loading

Description

This is the work to update our PC endpoint to receive a request but not batch it until subject has provided the ID verification code.

Refinement Notes

SR ID, PC ID, auth code -> if all these match then ID is verified.
hook into base logic to validate code
@adriaaaa adriaaaa changed the title Update PC endpoint to include ID verification flow Backend - Update PC endpoint to include ID verification flow Aug 10, 2022
@adriaaaa adriaaaa changed the title Backend - Update PC endpoint to include ID verification flow Backend - expose a verification endpoint Aug 16, 2022
@pattisdr
Copy link
Contributor

I'm going to split work a little differently:

#1062 - separate endpoint that verifies and then queues the privacy request
#1010 - generate code and send to the user when they attempt to create a privacy request and they have identity verification turned on.

This was referenced Aug 18, 2022
Closed
Merged
eastandwestwind pushed a commit that referenced this issue Aug 19, 2022
@pattisdr
Endpoint to Verify User Identity [#1062] (#1111)
9dbe9ef 
* Add an endpoint to verify a user's identity before queuing the privacy request provided it doesn't need separate manual approval by a system admin.

- Add a new PrivacyRequest.identity_verified_at timestamp
- Add a new PrivacyRequestStatus - "identity_unverified".
- Add methods to cache the verification code in Redis for comparison with a default ttl of 10 minutes

* - Fix linting/copy-paste errors.
- Update changelog.
- Add endpoint to postman

* Add new keys to response bodies.

* Instead of using a new VerificationCode schema, use the SubjectIdentityVerificationBodyParams that already exists.

* Revert "Instead of using a new VerificationCode schema, use the SubjectIdentityVerificationBodyParams that already exists."

This reverts commit 40fcf6d.
sanders41 pushed a commit that referenced this issue Sep 22, 2022
@pattisdr
Endpoint to Verify User Identity [#1062] (#1111)
5fdedfa 
* Add an endpoint to verify a user's identity before queuing the privacy request provided it doesn't need separate manual approval by a system admin.

- Add a new PrivacyRequest.identity_verified_at timestamp
- Add a new PrivacyRequestStatus - "identity_unverified".
- Add methods to cache the verification code in Redis for comparison with a default ttl of 10 minutes

* - Fix linting/copy-paste errors.
- Update changelog.
- Add endpoint to postman

* Add new keys to response bodies.

* Instead of using a new VerificationCode schema, use the SubjectIdentityVerificationBodyParams that already exists.

* Revert "Instead of using a new VerificationCode schema, use the SubjectIdentityVerificationBodyParams that already exists."

This reverts commit 40fcf6d.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pattisdr pattisdr

Labels
Subject Identity Verification
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Endpoint to Verify User Identity [#1062] ethyca/fidesops
3 participants
@NevilleS @pattisdr @adriaaaa