Skip to content

Token Use (Access) and Client Cred. and Res Own #556

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 7.1.x
Choose a base branch
from
Open

Token Use (Access) and Client Cred. and Res Own #556

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions ...eployment/articles/04-securing-liferay/15-oauth2/02-authorizing-access.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,17 +116,16 @@ pattern looks like this:

https://[hostname]/o/oauth2/token?grant_type=password&client_id=[client ID]&client_secret=[client secret]&username=[[email protected]]&password=

Users are prompted for their passwords, and upon successful log in, receive an
authorization code.
In both cases users are NOT prompted for their passwords and receive an directly an access token.

## Token Use
## Access Token Use

All flows above result in an access token that's sent by the authorization
server (@product@) to the client application. This token is sent in the response
for the client application to store and send along with any future request for
data.

For example, say the authorization code `946856e2b5ddf0928f6fc55f657bab73` was
For example, say the access token `946856e2b5ddf0928f6fc55f657bab73` was
sent to the client application. When the client requests data, this code must be
sent in each request header. Using a command line HTTP client such as Curl, you
could send a request like this:
Expand Down