87 lines
2.9 KiB
Markdown
87 lines
2.9 KiB
Markdown
|
---
|
||
|
|
id: 589a8eb3f9fc0f352b528e72
|
||
|
|
title: Implementation of Social Authentication III
|
||
|
|
challengeType: 2
|
||
|
forumTopicId: 301558
|
||
|
|
---
|
||
|
|
|
||
|
|
## Description
|
||
|
|
||
|
|
<section id='description'>
|
||
|
|
||
|
The final part of the strategy is handling the profile returned from GitHub. We need to load the user's database object if it exists, or create one if it doesn't, and populate the fields from the profile, then return the user's object. GitHub supplies us a unique <em>id</em> within each profile which we can use to search with to serialize the user with (already implemented). Below is an example implementation you can use in your project--it goes within the function that is the second argument for the new strategy, right below where <code>console.log(profile);</code> currently is:
|
||
|
|
|
||
|
|
```js
|
||
|
|
myDataBase.findOneAndUpdate(
|
||
|
|
{ id: profile.id },
|
||
|
|
{
|
||
|
|
$setOnInsert: {
|
||
|
|
id: profile.id,
|
||
|
|
name: profile.displayName || 'John Doe',
|
||
|
|
photo: profile.photos[0].value || '',
|
||
|
|
email: Array.isArray(profile.emails)
|
||
|
|
? profile.emails[0].value
|
||
|
|
: 'No public email',
|
||
|
|
created_on: new Date(),
|
||
|
|
provider: profile.provider || ''
|
||
|
|
},
|
||
|
|
$set: {
|
||
|
|
last_login: new Date()
|
||
|
|
},
|
||
|
|
$inc: {
|
||
|
|
login_count: 1
|
||
|
|
}
|
||
|
|
},
|
||
|
|
{ upsert: true, new: true },
|
||
|
|
(err, doc) => {
|
||
|
|
return cb(null, doc.value);
|
||
|
|
}
|
||
|
);
|
||
|
|
```
|
||
|
|
|
||
|
|
`findOneAndUpdate` allows you to search for an object and update it. If the object doesn't exist, it will be inserted and made available to the callback function. In this example, we always set `last_login`, increment the `login_count` by `1`, and only populate the majority of the fields when a new object (new user) is inserted. Notice the use of default values. Sometimes a profile returned won't have all the information filled out or the user will keep it private. In this case, you handle it to prevent an error.
|
||
|
|
|
||
|
|
You should be able to login to your app now--try it!
|
||
|
|
|
||
|
|
Submit your page when you think you've got it right. If you're running into errors, you can check out the project completed up to this point <a href='https://gist.github.com/camperbot/183e968f0e01d81dde015d45ba9d2745' target='_blank'>here</a>.
|
||
|
|
|
||
|
|
</section>
|
||
|
|
|
||
|
|
## Instructions
|
||
|
|
|
||
|
|
<section id='instructions'>
|
||
|
|
|
||
|
|
</section>
|
||
|
|
|
||
|
|
## Tests
|
||
|
|
|
||
|
|
<section id='tests'>
|
||
|
|
|
||
|
|
```yml
|
||
|
|
tests:
|
||
|
|
- text: GitHub strategy setup should be complete.
|
||
|
|
testString: getUserInput => $.get(getUserInput('url')+ '/_api/auth.js') .then(data => { assert.match(data, /GitHubStrategy[^]*myDataBase/gi, 'Strategy should use now use the database to search for the user'); assert.match(data, /GitHubStrategy[^]*return cb/gi, 'Strategy should return the callback function "cb"'); }, xhr => { throw new Error(xhr.statusText); })
|
||
|
|
```
|
||
|
|
|
||
|
|
</section>
|
||
|
|
|
||
|
|
## Challenge Seed
|
||
|
|
|
||
|
|
<section id='challengeSeed'>
|
||
|
|
|
||
|
|
</section>
|
||
|
|
|
||
|
|
## Solution
|
||
|
|
|
||
|
|
<section id='solution'>
|
||
|
|
|
||
|
|
```js
|
||
|
/**
|
||
|
|
Backend challenges don't need solutions,
|
||
|
|
because they would need to be tested against a full working project.
|
||
|
|
Please check our contributing guidelines to learn more.
|
||
|
|
*/
|
||
|
|
```
|
||
|
|
|
||
|
|
</section>
|