coolaj86/oauth3.js
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

update examples

Browse Source
This commit is contained in:
aj 2017-08-10 20:54:34 +00:00
parent 5b11e2bca2
commit 937a681c5d
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -81,7 +81,7 @@ function onClickLogin() {
console.info('Secure PPID (aka subject):', session.token.sub); console.info('Secure PPID (aka subject):', session.token.sub);
return oauth3.request({ return oauth3.request({
url: 'https://oauth3.org/api/org.oauth3.provider/inspect' url: 'https://oauth3.org/api/issuer@oauth3.org/inspect_token'
, session: session , session: session
}).then(function (resp) { }).then(function (resp) {
@ -239,7 +239,7 @@ function onClickLogin() {
console.info('Secure PPID (aka subject):', session.token.sub); console.info('Secure PPID (aka subject):', session.token.sub);
return OAUTH3.request({ return OAUTH3.request({
url: 'https://oauth3.org/api/org.oauth3.provider/inspect_token' url: 'https://oauth3.org/api/issuer@oauth3.org/inspect_token'
, session: session , session: session
}).then(function (resp) { }).then(function (resp) {
@ -464,10 +464,10 @@ 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`: However, we do have a problem of disambiguation since a URI may look like a `path`:
1. https://example.com/api/org.oauth3.provider 1. https://example.com/api/issuer@oauth3.org
2. example.com/api/org.oauth3.provider/ (not unique) 2. example.com/api/issuer@oauth3.org/ (not unique)
3. /api/org.oauth3.provider 3. /api/issuer@oauth3.org
4. api/org.oauth3.provider (not unique) 4. api/issuer@oauth3.org (not unique)
Therefore anywhere a URI or a Path could be used, the URI must be a URL. Therefore anywhere a URI or a Path could be used, the URI must be a URL.
We eliminate #2. We eliminate #2.