using NAR OAUTH server management plane


 

we were able to register a first client, entitled to seek an authorization code grant:

 

image

 

The values, distinct from the display name we entered as “clientid” are all generated values:

Name:
clientid(Subscribers will use this)

client_id:
7ClcPY1GXEephAZZ

client_secret:
gBtUn2I2o5gx38cVearV4WrKoVOcz1Jfr7r3OdlT

redirect_uri:
http://localhost/

we used the

image

image

 

 

Looking at the code, we see that each form post back to a route, registered in the setup:

 

image

image

 

This step is performed authorization server manager, of course, the custodian of the data (acting on behalf of the resource owner). The next step is performed by the administrative user of the client, who must authenticate to the AS in order to get the one time code – that seeds obtaining the first access token (and any refresh token):

image

image

For some reason, NAR refer to this process as one of “enablement”.

 

In another experiment, we can start to hook up the webapi server and authorization server.

Advertisements

About home_pw@msn.com

Computer Programmer who often does network administration with focus on security servers. Very strong in Microsoft Azure cloud!
This entry was posted in oauth. Bookmark the permalink.