32609e20fa
|
||
|---|---|---|
| bin | ||
| browserify | ||
| prefactor | ||
| well-known/oauth3 | ||
| .gitignore | ||
| .jshintrc | ||
| .npmignore | ||
| .well-known | ||
| README.md | ||
| bower.json | ||
| bump-versions.sh | ||
| dns.examples.js | ||
| gulpfile.js | ||
| oauth3.account.js | ||
| oauth3.core.js | ||
| oauth3.crypto.fallback.js | ||
| oauth3.crypto.fallback.min.js | ||
| oauth3.crypto.js | ||
| oauth3.dns.js | ||
| oauth3.domains.js | ||
| oauth3.issuer.js | ||
| oauth3.issuer.mock.js | ||
| oauth3.ng.js | ||
| oauth3.node.crypto.js | ||
| oauth3.node.js | ||
| oauth3.node.storage.js | ||
| oauth3.org.directives.json | ||
| oauth3.org.session.json | ||
| oauth3.tunnel.js | ||
| package.json | ||
README.md
oauth3.js
The world's smallest, fastest, and most secure OAuth3 (and OAuth2) JavaScript implementation (Yes! works in browsers and node.js with no extra dependencies or bloat and no hacks!)
Instead of bloating your webapp and ruining the mobile experience, you can use a single, small javascript file for all OAuth3 providers (and almost all OAuth2 providers) with a seamless experience.
Also, instead of complicated (or worse - insecure) CLI and Desktop login methods, you can easily integrate an OAuth3 flow (or broker) into any node.js app (i.e. Electron, Node-Webkit) with 0 pain.
If you have no idea what you're doing
(people who know what they're doing should skip ahead to the tl;dr instructions)
- Create a folder for your project named after your app, such as
example.com/ - Inside of the folder
example.com/a folder calledassets/ - Inside of the folder
example.com/assetsa folder calledorg.oauth3/ - Download oauth.js-v1.zip
- Double-click to unzip the folder.
- Copy the file
oauth3.core.jsinto the folderexample.com/assets/org.oauth3/ - Copy the folder
well-knowninto the folderexample.com/ - Rename the folder
well-knownto.well-known(when you do this, it become invisible, that's okay) - Add
<script src="assets/org.oauth3/oauth3.core.js"></script>to yourindex.html - Add
<script src="app.js"></script>to yourindex.html - Create files in
example.comcalledapp.jsandindex.htmland put this in it:
index.html:
<!DOCTYPE html>
<html>
<head>
</head>
<body>
<input type="url" placeholder="ex: https://oauth3.org" class="js-provider-uri">
<button type="button" class="js-login">Login</button>
<button type="button" class="js-logout">Logout</button>
<script src="https://code.jquery.com/jquery-3.1.1.js"
integrity="sha256-16cdPddA6VdVInumRGo6IbivbERE8p7CQR3HzTBuELA="
crossorigin="anonymous"></script>
<script src="assets/org.oauth3/oauth3.core.js"></script>
<script src="app.js"></script>
</body>
</html>
app.js:
var OAUTH3 = window.OAUTH3;
var auth = OAUTH3.create(window.location); // use window.location to set Client URI (your app's id)
// this is any OAuth3-compatible provider, such as oauth3.org
// in v1.1.0 we'll add backwards compatibility for facebook.com, google.com, etc
//
function onChangeProvider(_providerUri) {
// example https://oauth3.org
return auth.setProvider(providerUri);
}
// This opens up the login window for the specified provider
//
function onClickLogin() {
return auth.authenticate().then(function (session) {
console.info('Authentication was Successful:');
console.log(session);
// You can use the PPID (or preferably a hash of it) as the login for your app
// (it securely functions as both username and password which is known only by your app)
// If you use a hash of it as an ID, you can also use the PPID itself as a decryption key
//
console.info('Secure PPID (aka subject):', session.token.sub);
return auth.request({
url: 'https://oauth3.org/api/org.oauth3.provider/inspect'
, session: session
}).then(function (resp) {
console.info("Inspect Token:");
console.log(resp.data);
});
}, function (err) {
console.error('Authentication Failed:');
console.log(err);
});
}
// This opens up the logout window
//
function onClickLogout() {
return auth.logout().then(function () {
localStorage.clear();
console.info('Logout was Successful');
}, function (err) {
console.error('Logout Failed:');
console.log(err);
});
}
// initialize the provider to be oauth3.org (or any compatible provider)
//
onChangeProvider('oauth3.org');
$('body').on('click', '.js-login', onClickLogin);
$('body').on('click', '.js-logout', onClickLogout);
$('body').on('change', 'input.js-provider-uri', onChangeProvider);
Copy the example.com/ folder to your webserver.
Example
If you had a simple website / webapp for example.com with only the most necessary files,
it might look like this:
example.com
│
│
├── .well-known (hidden)
│ └── oauth3
│ ├── callback.html
│ ├── directives.json
│ └── index.html
├── assets
│ └── org.oauth3
│ └── oauth3.core.js
│
│
├── css
│ └── main.css
├── index.html
└── js
└── app.js
Installation (if you know what you're doing)
Advanced Installation with git
# Navigate to your web site or web app
pushd /path/to/your/web/app
# clone the project as assets/org.oauth3
mkdir -p assets
git clone git@git.daplie.com:Daplie/oauth3.js.git assets/org.oauth3
pushd assets/org.oauth3
git checkout v1
popd
# symlink `.well-known/oauth3` to `assets/org.oauth3/.well-known/oauth3`
mkdir -p .well-known
ln -sf ../assets/org.oauth3/.well-known/oauth3 .well-known/oauth3
Advanced Installation with bower
# Install to bower_components
bower install oauth3
# create a `.well-known` folder and an `assets` folder
mkdir -p .well-known assets
# symlink `.well-known/oauth3` to `bower_components/oauth3/.well-known/oauth3`
ln -sf ../bower_components/oauth3/.well-known/oauth3 .well-known/oauth3
# symlink `assets/org.oauth3` to `bower_components/oauth3`
ln -sf ../bower_components/oauth3/.well-known/oauth3 .well-known/oauth3
ln -sf ../bower_components/oauth3 assets/org.oauth3
Usage
Update your HTML to include the the following script tag:
<script src="assets/org.oauth3/oauth3.core.js"></script>
You can create a very simple demo application like this:
var providerUri;
var opts = { client_uri: OAUTH3.utils.clientUri(window.location) };
// this is any OAuth3-compatible provider, such as oauth3.org
// in v1.1.0 we'll add backwards compatibility for facebook.com, google.com, etc
//
function onChangeProvider(_providerUri) {
providerUri = _providerUri;
return OAUTH3.discover(providerUri, opts); // just to cache
}
// This opens up the login window for the specified provider
//
function onClickLogin() {
return OAUTH3.implicitGrant(providerUri, opts).then(function (session) {
console.info('Authentication was Successful:');
console.log(session);
// You can use the PPID (or preferably a hash of it) as the login for your app
// (it securely functions as both username and password which is known only by your app)
// If you use a hash of it as an ID, you can also use the PPID itself as a decryption key
//
console.info('Secure PPID (aka subject):', session.token.sub);
return OAUTH3.request({
url: 'https://oauth3.org/api/org.oauth3.provider/inspect_token'
, session: session
}).then(function (resp) {
console.info("Inspect Token:");
console.log(resp.data);
});
}, function (err) {
console.error('Authentication Failed:');
console.log(err);
});
}
// initialize the provider to be oauth3.org (or any compatible provider)
//
onChangeProvider('oauth3.org');
Compatibility with Frameworks and Libraries
jQuery:
You're all set. Nothing else is needed.
Angular 1:
We've created an Oauth3 service just for you:
<script src="assets/org.oauth3/oauth3.ng.js"></script>
You can include that in addition to the standard file or,
if you don't want an extra request, just paste it into your app.js.
Simple API
We include a small wrapper function of just a few lines in the bottom of oauth3.core.js
which exposes a create method to make using the underlying library require typing fewer keystrokes.
auth = OAUTH3.create(location); // takes a location object, such as window.location
// to create the Client URI (your app's id)
// and save it to an internal state
promise = auth.init(location); // set and fetch your own site/app's configuration details
// promises your site's config
promise = auth.setProvider(url); // changes the Provider URI (the site you're logging into),
// promises the provider's config // gets the config for that site (from their .well-known/oauth3),
// and caches it in internal state as the default
promise = auth.authenticate(); // opens login window for the provider and returns a session
// (must be called after the setProvider promise has completed)
promise = auth.authorize(permissions); // authenticates (if not authenticated) and opens a window to
// authorize a particular scope (contacts, photos, whatever)
promise = auth.request({ url, method, data }); // make an (authorized) request to a provider's resource
// (contacts, photos, whatever)
promise = auth.logout(); // opens logout window for the provider
auth.session(); // returns the current session, if any
Real API
OAUTH3.clientUri(window.location); // produces the default `client_uri` of your app (also used as `client_id`)
OAUTH3.discover(providerUri, { client_id: clientUri }); // Promises the config file for the provider and caches it in memory.
OAUTH3.implicitGrant(providerUri, { client_id: clientUri }) // returns a `session` with `session.token.sub` as the secure ppid.
// debug: true - will cause the windows to not refresh automatically
// windowType: 'popup' - will use a popup window to ask user for new permissions, if any
// windowType: 'background' - will automatically log the user in (if all permissions have been accepted)
OAUTH3.request({ method: 'GET', url: '', session: '', data: '' }) // make an authenticated request to a resource
OAUTH3.logout(providerUri, { client_id: clientUri, session: session }) // opens a popup to confirm logout from the provider
// Note: you should probably clear your own storage (i.e. localStorage, indexedDb) whenever you call this
OAUTH3.urls
.discover(providerUri, { client_id: clientUri }) // generates a correctly parameterized url
.implicitGrant(directives, { client_id: clientUri }) // generates a correctly parameterized url
.refreshToken(directives, opts) // generates a correctly parameterized url
// opts.client_id = clientUri
// opts.access_token = <jwt>
// opts.refresh_token = <jwt>
Core API (staging)
These APIs are NOT yet public, stable APIs, but they are good to be aware of and may help with debugging.
DO NOT rely on them. Many of them WILL change (we just wanted to publish with things as they are).
Public utilities for browser and node.js:
OAUTH3.jwt
.decode('<urlSafeBase64-encoded-json-web-token>'); // { iat, iss, aud, sub, exp, ttl }
OAUTH3
.query.stringify({ access_token: '...', debug: true }); // access_token=...&debug=true
.scope.stringify([ 'profile', 'contacts' ]); // 'profile,contacts'
.uri.normalize('https://oauth3.org/connect/'); // 'oauth3.org/connect'
.url.normalize('oauth3.org/connect/'); // 'https://oauth3.org/connect'
.url.resolve('oauth3.org/connect/', '/api/'); // 'https://oauth3.org/connect/api'
Issuer API (staging)
These additional methods are
OAUTH3
.query.parse('#/?foo=bar&baz=qux'); // { access_token: '...', debug: 'true' }
.scope.parse('profile,contacts'); // [ 'profile', 'contacts' ]
.url.redirect(clientParams, grants, tokenOrError); // securely redirect to client (or give security or other error)
Internal API
This APIs will absolutely change before they are made public
(at the very least the leading _ will be removed)
OAUTH3.jwt
.freshness(tokenMeta, staletimeSeconds, _now); // returns 'fresh', 'stale', or 'expired' (by seconds before expiry / ttl)
OAUTH3
.url._normalizePath('oauth3.org/connect/'); // 'oauth3.org/connect'
.randomState(); // a 128-bit crypto-random string
._insecureRandomState(); // a fallback for randomState() in old browsers
._base64.atob('<non-urlsafe-base64-string>'); // '<binary-string>' (typically json ascii)
._base64.decodeUrlSafe(b64); // makes base64 safe for window.atob and then calls atob
OAUTH3._browser // a collection of things a browser needs to perform requests
Roadmap
- v1.0 - "implicit grant" authorization with examples
- popup
- iframe
- documentation
- v1.1 - cleanup
- in-flow discovery
- smallest possible size
- inline windowing (non-promisable callback)
- async set/get
- logout
- v1.2 - features
- "authorization code" flow
- "broker" flow
- v1.3 - features
- remove grants
URL generation:
authorizationCodeauthorizationRedirectimplicitGrantloginCoderesourceOwnerPassword
URI vs URL
See https://danielmiessler.com/study/url-uri/#gs.=MngfAk
Since we do not require the protocol to be specified, it is a URI
However, we do have a problem of disambiguation since a URI may look like a path:
- https://example.com/api/org.oauth3.provider
- example.com/api/org.oauth.provider/ (not unique)
- /api/org.oauth3.provider
- api/org.oauth3.provider (not unique)
Therefore anywhere a URI or a Path could be used, the URI must be a URL. We eliminate #2.
As a general rule I don't like rules that sometimes apply and sometimes don't, so I may need to rethink this. However, there are cases where including the protocol can be very ugly and confusing and we definitely need to allow relative paths.
A potential work-around would be to assume all paths are relative (eliminate #4 instead) and have the path always key off of the base URL - if oauth3 directives are to be found at https://example.com/username/.well-known/oauth3/directives.json then /api/whatever would refer to https://example.com/username/api/whatever.