Skip to content

Commit 808a226

Browse files
committed
start intro with positive example instead of defining as the opposite of password auth
1 parent 125b9a4 commit 808a226

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

draft-ietf-oauth-v2-1.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -178,9 +178,20 @@ Framework described in RFC 6749 and the Bearer Token Usage in RFC 6750.
178178

179179
# Introduction {#introduction}
180180

181-
In the traditional client-server authentication model, the client
181+
OAuth introduces an authorization layer to the client-server authentication model
182+
by separating the role of the client from that of the resource
183+
owner. In OAuth, the client requests access to resources controlled
184+
by the resource owner and hosted by the resource server.
185+
Instead of using the resource owner's credentials to access protected
186+
resources, the client obtains an access token - a credential representing
187+
a specific set of access attributes such as scope and lifetime. Access
188+
tokens are issued to clients by an authorization server with the approval
189+
of the resource owner. The client uses the access token to access the
190+
protected resources hosted by the resource server.
191+
192+
In the older, more limited client-server authentication model, the client
182193
requests an access-restricted resource (protected resource) on the
183-
server by authenticating with the server using the resource owner's
194+
server by authenticating to the server using the resource owner's
184195
credentials. In order to provide applications access to
185196
restricted resources, the resource owner shares their credentials with
186197
the application. This creates several problems and limitations:
@@ -210,18 +221,7 @@ the application. This creates several problems and limitations:
210221
the end-user's password and all of the data protected by that
211222
password.
212223

213-
OAuth addresses these issues by introducing an authorization layer
214-
and separating the role of the client from that of the resource
215-
owner. In OAuth, the client requests access to resources controlled
216-
by the resource owner and hosted by the resource server.
217-
Instead of using the resource owner's credentials to access protected
218-
resources, the client obtains an access token - a credential representing
219-
a specific set of access attributes such as scope and lifetime. Access
220-
tokens are issued to clients by an authorization server with the approval
221-
of the resource owner. The client uses the access token to access the
222-
protected resources hosted by the resource server.
223-
224-
For example, an end-user (resource owner) can grant a printing
224+
With OAuth, an end-user (resource owner) can grant a printing
225225
service (client) access to their protected photos stored at a photo-
226226
sharing service (resource server), without sharing their username and
227227
password with the printing service. Instead, they authenticate

0 commit comments

Comments
 (0)