Skip to content

Gluu Gateway 4.0.x#


Gluu Gateway (GG) is Authentication and Authorization Management solution for APIs and websites based on OAuth2, OpenID Connect, UMA and OPA industry standards.

Gluu Gateway is based on Open Source Kong Gateway v1.3, and leverages the existing ecosystem of Kong plugins to enable rate limiting, logging, and many other capabilities.


  • GG requires an installation of the Gluu Server for OAuth2, UMA and OpenID Connect use cases.


Primary use cases and functionality supported by Gluu Gateway include:

  • Authentication by OAuth2/UMA bearer tokens and JWT
  • Authorization by OAuth/UMA scopes
  • Proxy websites, acting as an OpenID Connect Relying Party (RP)
  • Control access to API's by delegating the decision to an Open Policy Agent server (PDP)
  • Collect and report usage metrics
  • Provide a web GUI to simplify ongoing administration
  • Support Kong plugins to enable rate limiting, logging, and many other capabilities

Access Control#

Gluu Gateway functions as a policy enforcement point ("PEP"), relying on an external policy decision point ("PDP"). Gluu Gateway has two primary jobs:

  1. Validate tokens (both value and reference tokens)
  2. Make sure a request is authorized

Gluu Gateway supports both UMA and OAuth tokens. While mechanically the same, scopes have different meanings in UMA and OAuth.

UMA Authentication and scopes security#

UMA scopes represent centralized policy evaluation. For example, in the Gluu Server, administrators can map UMA scopes to policies, expressed as UMA RPT Authorization interception scripts.

UMA PEP diagram

OAuth Authentication and scopes security#

OAuth scopes normally represent a user's authorization, for example authorization to access a user's calendar. How scopes are granted is ultimately up to the Authorization Server that issues it.

OAuth PEP diagram

Open Policy Agent based policies#

In the Gluu Server, additional claims can be included in an access token. Gluu Gateway can forward this access token to an Open Policy Agent server for a policy decision.

OIDC and UMA with Claim gathering Security#

OpenID is an identity layer. The Gluu Gateway can act as an OpenID Relying Party, redirecting the subject's browser to the OpenID Provider, and obtaining user information. At that point, the Gluu Gateway can attempt to obtain an UMA access token, pushing the OpenID Connect id_token to the UMA RPT endpoint as input to the policy decision. If user interaction is required, the Gluu Gateway may redirect the subject to the UMA Authorization endpoint.


An API that uses OAuth for security can only be called by OAuth clients, and likewise, an API that uses UMA for security can only be called by an UMA client.

Clients v. Consumers#

In Gluu Gateway, a client_id is associated with a "Consumer" in Kong. This is useful where access control is restricted to certain clients. All other forms of client authentication are disabled in the Gluu Gateway Admin GUI -- we just want to use an OAuth Authorization Server like the Gluu Server for client authentication. The Gluu Server plugins verify the client_id for which a token was issued by looking at the JSON equivalent (either the JWT or the introspection response).


Gluu Gateway is available under the GLUU SUPPORT license.