oxd APIs#
Overview#
oxd offers an easy API for OAuth 2.0, OpenID Connect, and UMA 2.0.
-
The oxd OAuth APIs can be used to send a user to an OAuth 2.0 Authorization Server (AS) for authorization.
-
The oxd OpenID Connect APIs can be used to send a user to an OpenID Connect Provider (OP) for authentication and to gather identity information ("claims") about the user
-
The oxd UMA APIs can be used to send a user to an UMA Authorization Server (AS) for access policy enforcement, and are separated into two sections: UMA 2.0 Resource Server APIs and UMA 2.0 Client APIs.
OAuth 2.0 APIs#
Register Site#
The client must first register itself with the oxd-server.
If the registration is successful, oxd will dynamically register an OpenID Connect client and return an identifier for the application which must be presented in subsequent API calls. This is the oxd_id (not to be confused with the OpenID Connect Client ID).
register_site has many optional parameters.
The only required parameter is the redirect_uris which is list of Redirection URIs used by the Client. The first URL in this list is where the user will be redirected after successful authorization at the OpenID Connect Provider (OP).
The op_host parameter is optional, but it must be specified in either the default configuration file or the API call. This is the URL at the OP where users will be sent for authentication.
Note
op_host must point to a valid OpenID Connect Provider (OP) that supports Client Registration.
Update Site#
Update site modifies the client information on an OpenID Connect Provider (OP). The only required parameter for this operation is client's oxd_id parameter (which is generated during site registration). The other parameters are the same as the Register site parameters, except that op_host cannot be updated using this operation.
Remove Site#
Get Client Token#
Obtain an bearer access token from the oxd server. The OAuth 2.0 Authorization Framework: Bearer Token Usage.
The token should be used to access a protected resources.
Gluu-gateway supports only Authorization Request Header Field.
Oxd server is also protected by Authorization Request Header Field and the token must be used in all subsequent oxd queries.
The required parameters for /get-client-token are op_host, client_id and client_secret.
Get Access Token by Refresh Token#
A Refresh Token can be used to obtain a renewed Access Token.
Introspect Access Token#
This operation introspect if the client OAuth2 bearer access token obtained from the previous step is active or not.
Get User Info#
Use the access token from the step above to retrieve a JSON object with the user claims.
Get JSON Web Key Set#
This operation is used to get the JSON Web Key Set (JWKS) from OP host. The JWKS is a set of keys containing the public keys that should be used to verify any JSON Web Token (JWT) issued by the authorization server.
Get OP Discovery Configuration#
This operation fetches OP Discovery Configuration from OP host.
OpenID Connect APIs#
Get Authorization URL#
Returns the URL at the OpenID Connect Provider (OP) to which your application must redirect the person to authorize the release of personal data (and perhaps be authenticated in the process if no previous session exists).
The response from the OpenID Connect Provider (OP) will include the code and state values, which should be used to subsequently obtain tokens.
After redirecting to the above URL, the OpenID Connect Provider (OP) will return a response to the URL your application registered as the redirect URI (parse out the code and state). It will look like this:
HTTP/1.1 302 Found
Location: https://client.example.org/cb?code=SplxlOBeZQQYbYS6WxSbIA&state=af0ifjsldkj&scopes=openid%20profile
The only required parameter for /get-authorization-url is oxd_id. redirect_uri is a non-mandatory parameter in this command, if not provided then after authorization it will redirect to the first URL from redirect_uris list provided during client registration.
The custom parameters (in key and value pair) can be passed to OpenID Connect Provider (OP) using custom_parameters parameter. The standard parameters (in key and value pair) can be passed to OP using params parameter.
Get Tokens (ID & Access) by Code#
Use the code and state obtained in the previous step to call this API to retrieve tokens.
Get Logout URI#
The get_logout_uri command uses front-channel logout. A page is returned with iFrames, each of which contains the logout URL of the applications that have a session in that browser.
These iFrames should be loaded automatically, enabling each application to get a notification of logout, and to hopefully clean up any cookies in the person's browser. If the person blocks third-party cookies in their browser, front-channel logout will not work.
UMA 2 Resource Server APIs#
Your client, acting as an OAuth2 Resource Server, MUST:
- Register a protected resource (with the
uma_rs_protectcommand) - Intercept the HTTP call (before the actual REST resource call) and check the
uma_rs_check_accesscommand response to determine whether the requester is allowed to proceed or should be rejected:- Allow access: if the response from
uma_rs_check_accessisallowedornot_protected, an error is returned. - If
uma_rs_check_accessreturnsdeniedthen return back HTTP response.
- Allow access: if the response from
- client must have the
client_credentialsgrant type. It's required for correct PAT obtaining.
The uma_rs_check_access operation checks access using the "or" rule when evaluating scopes.
For example, a resource like /photo protected with scopes read, all (by uma_rs_protect command) assumes that if either read or all is present, access is granted.
If the "and" rule is preferred, it can be achieved by adding an additional scope, for example:
Resource1 scopes: read, write (follows the "or" rule).
Resource2 scopes: read_write (and associate read and write policies with the read_write scope)
If access is not granted, an unauthorized HTTP code and registered ticket are returned (ticket is re-newed if need_info is returned on /uma-rp-get-rpt). For example:
HTTP/1.1 401 Unauthorized
WWW-Authenticate: UMA realm="example",
as_uri="https://as.example.com",
ticket="016f84e8-f9b9-11e0-bd6f-0021cc6004de"
The uma_rs_check_access returns denied then returns back an HTTP response:
HTTP/1.1 403 Forbidden
Warning: 199 - "UMA Authorization Server Unreachable"
UMA RS Protect Resources#
It's important to have a single HTTP method mentioned only one time within a given path in JSON, otherwise the operation will fail.
Request:
POST /uma-rs-protect
{
"oxd_id":"6F9619FF-8B86-D011-B42D-00CF4FC964FF", <- REQUIRED
"overwrite":false, <- OPTIONAL oxd_id registers resource, if send uma_rs_protect second time with same oxd_id and overwrite=false then it will fail with error uma_protection_exists. overwrite=true means remove existing UMA Resource and register new based on JSON Document.
"resources":[ <- REQUIRED
{
"path":"/photo",
"conditions":[
{
"httpMethods":["GET"],
"scopes":[
"http://photoz.example.com/dev/actions/view"
]
},
{
"httpMethods":["PUT", "POST"],
"scopes":[
"http://photoz.example.com/dev/actions/all",
"http://photoz.example.com/dev/actions/add"
],
"ticketScopes":[
"http://photoz.example.com/dev/actions/add"
]
}
]
},
{
"path":"/document",
"conditions":[
{
"httpMethods":["GET"],
"scopes":[
"http://photoz.example.com/dev/actions/view"
]
}
]
}
]
}
Request with scope_expression. scope_expression is a Gluu-invented extension that allows a JsonLogic expression instead of a single list of scopes. Read more about scope_expression here.
POST /uma-rs-protect
{
"oxd_id": "6F9619FF-8B86-D011-B42D-00CF4FC964FF", <- REQUIRED
"overwrite":false, <- OPTIONAL oxd_id registers resource, if send uma_rs_protect second time with same oxd_id and overwrite=false then it will fail with error uma_protection_exists. overwrite=true means remove existing UMA Resource and register new based on JSON Document.
"resources": [ <- REQUIRED
{
"path": "/photo",
"conditions": [
{
"httpMethods": [
"GET"
],
"scope_expression": {
"rule": {
"and": [
{
"or": [
{
"var": 0
},
{
"var": 1
}
]
},
{
"var": 2
}
]
},
"data": [
"http://photoz.example.com/dev/actions/all",
"http://photoz.example.com/dev/actions/add",
"http://photoz.example.com/dev/actions/internalClient"
]
}
},
{
"httpMethods": [
"PUT",
"POST"
],
"scope_expression": {
"rule": {
"and": [
{
"or": [
{
"var": 0
},
{
"var": 1
}
]
},
{
"var": 2
}
]
},
"data": [
"http://photoz.example.com/dev/actions/all",
"http://photoz.example.com/dev/actions/add",
"http://photoz.example.com/dev/actions/internalClient"
]
}
}
]
}
]
}
UMA RS Check Access#
Operation to check whether access can be granted or not.
Request:
POST /uma-rs-check-access
{
"oxd_id":"6F9619FF-8B86-D011-B42D-00CF4FC964FF",
"rpt":"eyJ0 ... NiJ9.eyJ1c ... I6IjIifX0.DeWt4Qu ... ZXso", <-- REQUIRED - RPT or blank value if not sent by RP
"path":"<path of resource>", <-- REQUIRED - Resource Path (e.g. http://rs.com/phones), /phones should be passed
"http_method":"<http method of RP request>" <-- REQUIRED - HTTP method of RP request (GET, POST, PUT, DELETE)
}
Sample of RP Request:
GET /users/alice/album/photo HTTP/1.1
Authorization: Bearer vF9dft4qmT
Host: photoz.example.com
Parameters:
rpt: 'vF9dft4qmT'
path: /users/alice/album/photo
http_method: GET
Access Granted Response:
HTTP/1.1 200 OK
{
"access":"granted"
}
Access Denied with Ticket Response:
HTTP/1.1 200 OK
{
"access":"denied"
"www-authenticate_header":"UMA realm=\"example\",
as_uri=\"https://as.example.com\",
error=\"insufficient_scope\",
ticket=\"016f84e8-f9b9-11e0-bd6f-0021cc6004de\"",
"ticket":"016f84e8-f9b9-11e0-bd6f-0021cc6004de"
}
Access Denied without Ticket Response:
HTTP/1.1 200 OK
{
"access":"denied"
}
Resource is not Protected Error Response:
HTTP/1.1 400 Bad request
{
"error":"invalid_request",
"error_description":"Resource is not protected. Please protect your resource first with uma_rs_protect command."
}
UMA Introspect RPT#
Example of successful response:
HTTP/1.1 200 OK
{
"active":true,
"exp":1256953732,
"iat":1256912345,
"permissions":[
{
"resource_id":"112210f47de98100",
"resource_scopes":[
"view",
"http://photoz.example.com/dev/actions/print"
],
"exp":1256953732
}
]
}
UMA 2 Relying Party APIs#
UMA RP - Get RPT#
If your application is calling UMA 2 protected resources, use these APIs to obtain an RPT token.
Successful Response:
HTTP 1.1 200 OK
{
"access_token":"SSJHBSUSSJHVhjsgvhsgvshgsv",
"token_type":"Bearer",
"pct":"c2F2ZWRjb25zZW50",
"upgraded":true
}
If Need Info Error reponse is returned, then old ticket is invalidated and new ticket is returned inside Need Info Reponse. Make sure always new ticket is used.
Needs Info Error Response:
HTTP 1.1 403 Forbidden
{
"error": "need_info",
"ticket": "38569d82-6e4a-4287-aac8-1d9ea2b8c439",
"required_claims": [
{
"issuer": [
"https://gluu.local.org"
],
"name": "country",
"claim_token_format": [
"http://openid.net/specs/openid-connect-core-1_0.html#IDToken"
],
"claim_type": "string",
"friendly_name": "country"
},
{
"issuer": [
"https://gluu.local.org"
],
"name": "city",
"claim_token_format": [
"http://openid.net/specs/openid-connect-core-1_0.html#IDToken"
],
"claim_type": "string",
"friendly_name": "city"
}
],
"redirect_user": "https://gluu.local.org/oxauth/restv1/uma/gather_claims?customUserParam2=value2&customUserParam1=value1&client_id=@!B28D.DF29.C16D.8E6F!0001!5489.C322!0008!7946.30C2.ACFC.73D8&ticket=38569d82-6e4a-4287-aac8-1d9ea2b8c439"
}
UMA RP - Get Claims-Gathering URL#
ticket parameter for this command MUST be newest, in 90% cases it is from need_info error.
After being redirected to the Claims Gathering URL, the user goes through the claims gathering flow. If successful, the user is redirected back to claims_redirect_uri with a new ticket which should be provided with the next uma_rp_get_rpt call.
Example of Response:
https://client.example.com/cb?ticket=e8e7bc0b-75de-4939-a9b1-2425dab3d5ec
API References#
oxd has defined swagger specification here.
It is possible to generated native library in your favorite language by Swagger Code Generator
Check our FAQ about easiest way to generate native client here.