the current process solely happens at login. if a user is authed in through linkedin we get their linkedin ids and resolve them. if the email they use is returned by full contact with a linked in id we can resolve them. the old app had an authorize linkedin call that hit the profile app and returned and id to resolve the user.
Context
We need _summary data from a user in our database to display commonalities. the best way to do this is to match an existing linked in profile.
Possible Implementation
[x] auth0 returns linkedin id that is used to resolve. this can come from full contact or from linkedin auth
[ ] if not linkedin profile, when a user uploads the linkedin zip file we can use this to recreate a linkedin profile. this can be shipped to ers to try to resolve or to create a new prospect record which should be enriched to the fullest. the data should be stored in _details on the user record.
[ ] if still no linkedin profile we need to allow a user to authorize hitting the linkedin profile api to get their profile. this should be stored in els and _details on the user record.
[ ] if still no linkedin profile we need to hit all our data providers to create a full profile. this will be stored in the _details section of user recored as well as back into els
Detailed Description
the current process solely happens at login. if a user is authed in through linkedin we get their linkedin ids and resolve them. if the email they use is returned by full contact with a linked in id we can resolve them. the old app had an authorize linkedin call that hit the profile app and returned and id to resolve the user.
Context
We need _summary data from a user in our database to display commonalities. the best way to do this is to match an existing linked in profile.
Possible Implementation