Socket
Socket
Sign inDemoInstall

@feathersjs/authentication-oauth1

Package Overview
Dependencies
5
Maintainers
4
Versions
14
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

Comparing version 1.0.2 to 1.0.3

12

CHANGELOG.md
# Change Log
## [v1.0.2](https://github.com/feathersjs/authentication-oauth1/tree/v1.0.2) (2017-11-16)
[Full Changelog](https://github.com/feathersjs/authentication-oauth1/compare/v1.0.1...v1.0.2)
**Closed issues:**
- No error handler? [\#34](https://github.com/feathersjs/authentication-oauth1/issues/34)
**Merged pull requests:**
- Add default ES module default exports to make TypeScript integration … [\#37](https://github.com/feathersjs/authentication-oauth1/pull/37) ([daffl](https://github.com/daffl))
- Update @feathersjs/authentication to the latest version 🚀 [\#36](https://github.com/feathersjs/authentication-oauth1/pull/36) ([greenkeeper[bot]](https://github.com/apps/greenkeeper))
## [v1.0.1](https://github.com/feathersjs/authentication-oauth1/tree/v1.0.1) (2017-11-06)

@@ -4,0 +16,0 @@ [Full Changelog](https://github.com/feathersjs/authentication-oauth1/compare/v1.0.0...v1.0.1)

9

package.json
{
"name": "@feathersjs/authentication-oauth1",
"description": "A Feathers OAuth1 authentication strategy",
"version": "1.0.2",
"version": "1.0.3",
"homepage": "https://github.com/feathersjs/authentication-oauth1",

@@ -38,4 +38,3 @@ "main": "lib/",

"coverage": "istanbul cover node_modules/mocha/bin/_mocha -- --opts mocha.opts",
"test": "npm run lint && npm run coverage",
"start": "npm run compile && node example/app"
"test": "npm run lint && npm run coverage"
},

@@ -64,3 +63,3 @@ "semistandard": {

"express-session": "^1.14.2",
"feathers-memory": "^1.1.0",
"feathers-memory": "^2.0.0",
"istanbul": "^1.1.0-alpha.1",

@@ -70,3 +69,3 @@ "mocha": "^4.0.0",

"passport-twitter": "^1.0.4",
"semistandard": "^11.0.0",
"semistandard": "^12.0.0",
"sinon": "^4.0.0",

@@ -73,0 +72,0 @@ "sinon-chai": "^2.11.0"

@@ -18,114 +18,26 @@ # @feathersjs/authentication-oauth1

**Note:** This is only compatibile with `feathers-authentication@1.x` and above.
## Quick example
## Documentation
Please refer to the [@feathersjs/authentication-oauth1 documentation](http://docs.feathersjs.com/) for more details.
## Supported Strategies
There aren't a ton of OAuth1 strategies anymore as most have moved to OAuth2, however this will work for any [Passport OAuth1 strategy](http://passportjs.org/). Most notably [Twitter](https://github.com/jaredhanson/passport-twitter).
## API
This module contains 2 core pieces:
1. The main entry function
2. The `Verifier` class
### Main Initialization
In most cases initializing the `@feathersjs/authentication-oauth1` module is as simple as doing this:
```js
const feathers = require('@feathersjs/feathers');
const authentication = require('feathers-authentication');
const jwt = require('feathers-authentication-jwt');
const oauth1 = require('@feathersjs/authentication-oauth1');
const session = require('express-session');
const TwitterStrategy = require('passport-twitter').Strategy;
app.use(session({ secret: 'super secret', resave: true, saveUninitialized: true }));
app.configure(authentication(settings));
app.configure(oauth1({
name: 'twitter',
Strategy: TwitterStrategy,
consumerKey: '<your consumer key>',
consumerSecret: '<your consumer secret>'
}));
```
const app = feathers();
This will set up session middleware and authentication pulling from your global `auth` object in your config file. It will also mix in the following defaults, which can be customized.
#### Default Options
```js
{
idField: '<provider>Id', // The field to look up the entity by when logging in with the provider. Defaults to '<provider>Id' (ie. 'twitterId').
path: '/auth/<provider>', // The route to register the middleware
callbackPath: '/auth/<provider>/callback', // The route to register the callback handler
callbackURL: 'http(s)://hostame[:port]/auth/<provider>/callback', // The callback url. Will automatically take into account your host and port and whether you are in production based on your app environment to construct the url. (ie. in development http://localhost:3030/auth/twitter/callback)
entity: 'user', // the entity that you are looking up
service: 'users', // the service to look up the entity
passReqToCallback: true, // whether the request object should be passed to `verify`
session: true // whether to use sessions,
handler: function, // Express middleware for handling the oauth callback. Defaults to the built in middleware.
formatter: function, // The response formatter. Defaults the the built in feathers-rest formatter, which returns JSON.
Verifier: Verifier // A Verifier class. Defaults to the built-in one but can be a custom one. See below for details.
}
```
Additional passport strategy options can be provided based on the OAuth1 strategy you are configuring.
### Verifier
This is the verification class that handles the OAuth1 verification by looking up the entity (normally a `user`) on a given service and either creates or updates the entity and returns them. It has the following methods that can all be overridden. All methods return a promise except `verify`, which has the exact same signature as [passport-oauth1](https://github.com/jaredhanson/passport-oauth1).
```js
{
constructor(app, options) // the class constructor
_updateEntity(entity) // updates an existing entity
_createEntity(entity) // creates an entity if they didn't exist already
_normalizeResult(result) // normalizes result from service to account for pagination
verify(req, accessToken, refreshToken, profile, done) // queries the service and calls the other internal functions.
}
```
#### Customizing the Verifier
The `Verifier` class can be extended so that you customize it's behavior without having to rewrite and test a totally custom local Passport implementation. Although that is always an option if you don't want use this plugin.
An example of customizing the Verifier:
```js
import oauth1, { Verifier } from '@feathersjs/authentication-oauth1';
class CustomVerifier extends Verifier {
// The verify function has the exact same inputs and
// return values as a vanilla passport strategy
verify(req, accessToken, refreshToken, profile, done) {
// do your custom stuff. You can call internal Verifier methods
// and reference this.app and this.options. This method must be implemented.
// the 'user' variable can be any truthy value
done(null, user);
}
}
app.configure(oauth1({
name: 'twitter'
Strategy: TwitterStrategy,
consumerKey: '<your consumer key>',
consumerSecret: '<your consumer secret>',
Verifier: CustomVerifier
// Setup in memory session
app.use(session({
secret: 'super secret',
resave: true,
saveUninitialized: true
}));
```
## Customizing The OAuth Response
Whenever you authenticate with an OAuth1 provider such as Twitter, the provider sends back an `accessToken`, `refreshToken`, and a `profile` that contains the authenticated entity's information based on the OAuth1 `scopes` you have requested and been granted.
By default the `Verifier` takes everything returned by the provider and attaches it to the `entity` (ie. the user object) under the provider name. You will likely want to customize the data that is returned. This can be done by adding a `before` hook to both the `update` and `create` service methods on your `entity`'s service.
```js
// Setup authentication
app.configure(authentication(settings));
app.configure(jwt());
app.configure(oauth1({
name: 'twitter',
entity: 'user',
service: 'users',
Strategy,
Strategy: TwitterStrategy,
consumerKey: '<your consumer key>',

@@ -135,30 +47,9 @@ consumerSecret: '<your consumer secret>'

function customizeTwitterProfile() {
return function(hook) {
console.log('Customizing Twitter Profile');
// If there is a twitter field they signed up or
// signed in with twitter so let's pull the email. If
if (hook.data.twitter) {
hook.data.email = hook.data.twitter.email;
}
// If you want to do something whenever any OAuth
// provider authentication occurs you can do this.
if (hook.params.oauth) {
// do something for all OAuth providers
}
if (hook.params.oauth.provider === 'twitter') {
// do something specific to the twitter provider
}
return Promise.resolve(hook);
};
}
app.service('users').hooks({
// Setup a hook to only allow valid JWTs to authenticate
// and get new JWT access tokens
app.service('authentication').hooks({
before: {
create: [customizeTwitterProfile()],
update: [customizeTwitterProfile()]
create: [
authentication.hooks.authenticate(['jwt'])
]
}

@@ -168,48 +59,10 @@ });

## Complete Example
## Documentation
Here's a basic example of a Feathers server that uses `@feathersjs/authentication-oauth1`. You can see a fully working example in the [example/](./example/) directory.
Please refer to the [@feathersjs/authentication-oauth1 documentation](http://docs.feathersjs.com/) for more details.
**Note:** You must setup some session middleware. OAuth1 strategies rely on sessions in order to authenticate.
```js
const feathers = require('feathers');
const rest = require('feathers-rest');
const hooks = require('feathers-hooks');
const memory = require('feathers-memory');
const bodyParser = require('body-parser');
const session = require('express-session');
const TwitterStrategy = require('passport-twitter').Strategy;
const errorHandler = require('feathers-errors/handler');
const auth = require('feathers-authentication');
const oauth1 = require('@feathersjs/authentication-oauth1');
// Initialize the application
const app = feathers()
.configure(rest())
// Needed for parsing bodies (login)
.use(bodyParser.json())
.use(bodyParser.urlencoded({ extended: true }))
// set up session support. This is required for OAuth1 strategies
.use(session({ secret: 'super secret', resave: true, saveUninitialized: true }))
// Configure feathers-authentication
.configure(auth({ secret: 'super secret' }))
.configure(oauth1({
name: 'twitter',
Strategy: TwitterStrategy,
consumerKey: '<your consumer key>',
consumerSecret: '<your consumer secret>'
}))
.use('/users', memory())
.use(errorHandler());
app.listen(3030);
console.log('Feathers app started on 127.0.0.1:3030');
```
## License
Copyright (c) 2016
Copyright (c) 2018
Licensed under the [MIT license](LICENSE).
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc