User Story:

As a Passport user, I want to connect my LinkedIn account using the new API (V2) so that I can verify my email address and ensure accurate profile data.

Acceptance Criteria

GIVEN a user connecting their LinkedIn account,
WHEN they use the OAuth flow,
THEN the system should retrieve both the unique user identifier and email verification status using LinkedIn API V2.
AND any LinkedIn Stamp in our DB from V1 should be removed or marked as expired/revoked during the cutover.

GIVEN a user lost their v1 Linkedin Stamp,
WHEN they enter the Passport app,
THEN they should see a targeted notification letting them that they need to re-verify their LinkedIn stamp because of a change with the LinkedIn API.

Product & Design Links:

N/A

Tech Details:

• Update existing LinkedIn provider to utilize API V2.
• Adjust IAM logic to check for verified email status.
• Ensure unique user identifiers from V2 are used for future deduplication.
• Remove or mark expired/revoked existing LinkedIn Stamps in DB during cutover.

Open Questions:

• Any additional data points from V2 to consider?
• Specific users or segments to inform about this change?

Notes/Assumptions:

• Ignore historical data from LinkedIn API V1.
• Manage the transition period, addressing potential temporary duplication.