Skip to content

Describe access-token invalidation - #258

Merged
crandmck merged 4 commits into
gh-pagesfrom
doc/access-token-invalidation
Jan 28, 2017
Merged

crandmck merged 4 commits into
gh-pagesfrom
doc/access-token-invalidation

Conversation

@bajtos

@bajtos bajtos commented Jan 26, 2017

Copy link
Copy Markdown
Member

@crandmck please review, feel free to make any edits directly

See also strongloop/loopback#3112

@bajtos
bajtos requested a review from crandmck January 26, 2017 12:28
@bajtos bajtos added the review label Jan 26, 2017
`"logoutSessionsOnSensitiveChanges`" to `true` in `server/config.json` file.

{% include tip.html content="
If your application implements an own solution for access-token invalidation, then set `logoutSessionsOnSensitiveChanges` to `false`, to prevent interference between the built-in invalidation and your custom solution. This will also disable the warning. However, note that this flag is not available in LoopBack 3.x.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"If your application implements an own solution for access-token invalidation.." > "If your application implements access-token invalidation itself .. "

sessions, one has to enable context propagation via "options" argument
in the settings of your User model. This setting cannot be changed in the
built-in User model, the application must configure a custom model [extending
the built-in `User` model](Extending-built-in-models.html).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"You cannot change this setting in the built-in User model. Instead, configure a custom model that extends the built-in User model.

Comment thread pages/en/lb3/Managing-users.md Outdated
When user's account is compromised, for example when their password is leaked,
or the attacker gains access to their email account, the user need means for
recovering from the situation and preventing the attacker from continued use
of the services under the attacked user's name.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"When a user's account is compromised (for example their password is leaked or the attacker gains access to their email account), the app needs to be able to prevent continued use of the hijacked account."

@crandmck

Copy link
Copy Markdown
Contributor

I went ahead and edited the files in the branch. Now LGTM!

@crandmck
crandmck merged commit 9bdad00 into gh-pages Jan 28, 2017
@crandmck crandmck removed the review label Jan 28, 2017
@crandmck
crandmck deleted the doc/access-token-invalidation branch January 28, 2017 00:40
@bajtos

bajtos commented Jan 30, 2017

Copy link
Copy Markdown
Member Author

I went ahead and edited the files in the branch. Now LGTM!

@crandmck awesome 🎉 thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants