Authlete OAuth 2.0 & OpenID Connect

Getting Started

1. Direct the user to the authorization endpoint. Your client initiates the OAuth flow by redirecting the user to the authorization server.

   curl -v "http://localhost:3000/api/authorization?response_type=code&client_id=YOUR_CLIENT_ID&redirect_uri=YOUR_REDIRECT_URI&scope=openid+profile&state=xyz"

2. The user signs in and grants consent. The server redirects back to your app with an authorization code.

   GET /callback?code=abc123&state=xyz

3. Exchange the authorization code for a token at the token endpoint.

   curl -X POST "http://localhost:3000/api/token" \
     -H "Content-Type: application/x-www-form-urlencoded" \
     -d "grant_type=authorization_code&code=abc123&redirect_uri=YOUR_REDIRECT_URI&client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET"

4. Use the access token to call the UserInfo endpoint and other protected resources.

   curl "http://localhost:3000/api/userinfo" \
     -H "Authorization: Bearer YOUR_ACCESS_TOKEN"

5. Refresh the access token when it expires using the refresh token.

   curl -X POST "http://localhost:3000/api/token" \
     -H "Content-Type: application/x-www-form-urlencoded" \
     -d "grant_type=refresh_token&refresh_token=YOUR_REFRESH_TOKEN&client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET"

About This Server

• Authlete is an OAuth 2.0 & OpenID Connect implementation on cloud.
• This authorization server is written using Authlete's open source libraries.
• DB-less — authorization data are stored on cloud via Authlete.
• Manage settings via Service Owner Console.
• Manage client applications via Developer Console.