This is a resource server implementation in Go. It supports a userinfo endpoint defined in OpenID Connect Core 1.0 and includes an example of a protected resource endpoint that accepts an access token in the way defined in 2.1. Authorization Request Header Field of RFC 6750 (The OAuth 2.0 Authorization Framework: Bearer Token Usage).
This implementation is written using Gin and authlete-go-gin library which is an Anthlete's open-source library for Gin.
To validate an access token presented by a client application, this resource server makes an inquiry to the Authlete server. This means that this resource server expects that the authorization server which has issued the access token uses Authlete as a backend service. gin-oauth-server is such an authorization server implementation and it supports OAuth 2.0 and OpenID Connect.
Apache License, Version 2.0
https://github.com/authlete/gin-resource-server
Authlete is a cloud service that provides an implementation of OAuth 2.0 & OpenID Connect (overview). You can easily get the functionalities of OAuth 2.0 and OpenID Connect either by using the default implementation provided by Authlete or by implementing your own authorization server using Authlete Web APIs.
To use this resource server implementation, you need to get API credentials
from Authlete and set them in authlete.toml. The steps to get API credentials
are very easy. All you have to do is just to register your account
(sign up). See Getting Started for
details.
-
Install authlete-go and authlete-go-gin libraries.
$ go get github.com/authlete/authlete-go $ go get github.com/authlete/authlete-go-gin -
Download the source code of this resource server implementation.
$ git clone https://github.com/authlete/gin-resource-server.git $ cd gin-resource-server -
Edit the configuration file to set the API credentials of yours.
$ vi authlete.toml -
Build the resource server.
$ make -
Start the resource server on
http://localhost:8081.$ make run
This implementation exposes endpoints as listed in the table below.
| Endpoint | Path |
|---|---|
| UserInfo Endpoint | /api/userinfo |
| Time Endpoint | /api/time |
The userinfo endpoint is an implementation of the requirements described in 5.3. UserInfo Endpoint of OpenID Connect Core 1.0.
The endpoint returns user information in JSON or JWT format, depending on the
configuration of the client application. If both userinfo_signed_response_alg
and userinfo_encrypted_response_alg of the metadata of the client application
are not specified, user information is returned as a plain JSON. Otherwise, it
is returned as a serialized JWT. Authlete provides you with a Web console
(Developer Console) to manage metadata of client applications.
As for metadata of client applications, see 2. Client Metadata
of OpenID Connect Dynamic Client Registration 1.0.
User information returned from the endpoint contains claims
of the user. In short, claims are pieces of information about the user such
as a given name and an email address. Because Authlete does not manage user
data (although it supports OpenID Connect), you have to provide claim values.
It is achieved by implementing UserInfoReqHandlerSpi interface.
In this resource server implementation, UserInfoReqHandlerSpiImpl is an
example implementation of UserInfoReqHandlerSpi interface and it retrieves
claim values from the dummy user database (user_management.go).
The time endpoint implemented in this resource server is just an example of a protected resource endpoint. Its main purpose is to show how to validate an access token at a protected resource endpoint.
The path of the time endpoint is /api/time. The endpoint accepts an access
token in the way defined in 2.1. Authorization Request Header Field
of RFC 6750.
$ ACCESS_TOKEN=YOUR_ACCESS_TOKEN
$ curl -v http://localhost:8081/api/time \
-H "Authorization: Bearer ${ACCESS_TOKEN}"
The time endpoint returns information about the current time in JSON format. The following is an example response.
{
"year": 2019,
"month": 8,
"day": 9,
"hour": 14,
"minute": 45,
"second": 2
}
As for generic and Authlete-specific information regarding how to protect Web APIs by OAuth 2.0 access tokens, see Protected Resource.
- Authlete - Authlete Home Page
- authlete-go - Authlete Library for Go
- authlete-go-gin - Authlete Library for Gin
- gin-oauth-server - Authorization Server Implementation
Contact Form : https://www.authlete.com/contact/
| Purpose | Email Address |
|---|---|
| General | info@authlete.com |
| Sales | sales@authlete.com |
| PR | pr@authlete.com |
| Technical | support@authlete.com |