Kubernetes-native authorization service for tailor-made Zero Trust API security.
A lightweight Envoy external authorization server fully manageable via Kubernetes Custom Resources.
JWT authentication, API key, mTLS, pattern-matching authz, OPA, K8s SA tokens, K8s RBAC, external metadata fetching, and more, with minimum to no coding at all, no rebuilding of your applications.
Authorino is not about inventing anything new. It's about making the best things about auth out there easy and simple to use. Authorino is multi-tenant, it's cloud-native and it's open source.
- Deploy with the Authorino Operator
- Setup Envoy proxy and the external authorization filter
- Apply an Authorino
- Obtain an authentication token and start sending requests
The full Getting started page of the docs provides details for the steps above, as well as information about requirements and next steps.
Or try out our Hello World example.
For general information about protecting your service using Authorino, check out the docs.
The User guides section of the docs gathers several AuthN/AuthZ use-cases as well as the instructions to implement them using Authorino. A few examples are:
- Authentication with JWTs and OpenID Connect Discovery
- Authentication with API keys
- Authentication with Kubernetes SA tokens (TokenReview API)
- Authentication with X.509 certificates and mTLS
- Authorization with JSON pattern-matching rules (e.g. JWT claims, request attributes, etc)
- Authorization with Open Policy Agent (OPA) Rego policies
- Authorization using the Kubernetes RBAC (rules stated in K8s
- Authorization using auth metadata fetched from external sources
- OIDC authentication and RBAC with Keycloak JWTs
- Injecting auth data into the request (HTTP headers, Wristband tokens, rate-limit metadata, etc)
- Authorino for the Kubernetes control plane (aka Authorino as ValidatingWebhook service)
How it works
Authorino enables hybrid API security, with usually no code changes required to your application, tailor-made for your own combination of authentication standards and protocols and authorization policies of choice.
Bootstrap and configuration:
- Deploy the service/API to be protected ("Upstream"), Authorino and Envoy
- Write and apply an Authorino
AuthConfigCustom Resource associated to the public host of the service
- A user or service account ("Consumer") obtains an access token to consume resources of the Upstream service, and sends a request to the Envoy ingress endpoint
- The Envoy proxy establishes fast gRPC connection with Authorino carrying data of the HTTP request (context info), which causes Authorino to lookup for an
AuthConfigCustom Resource to enforce (pre-cached)
- Identity verification (authentication) phase - Authorino verifies the identity of the consumer, where at least one authentication method/identity provider must go through
- External metadata phase - Authorino fetches additional metadata for the authorization from external sources (optional)
- Policy enforcement (authorization) phase - Authorino takes as input a JSON composed out of context data, resolved identity object and fetched additional metadata from previous phases, and triggers the evaluation of user-defined authorization policies
- Response (metadata-out) phase – Authorino builds user-defined custom responses (dynamic JSON objects and/or Festival Wristband OIDC tokens), to be supplied back to the client and/or upstream service within added HTTP headers or as Envoy Dynamic Metadata (optional)
- Callbacks phase – Authorino sends callbacks to specified HTTP endpoints (optional)
- Authorino and Envoy settle the authorization protocol with either OK/NOK response
- If authorized, Envoy triggers other HTTP filters in the chain (if any), pre-injecting eventual dynamic metadata returned by Authorino, and ultimately redirects the request to the Upstream
- The Upstream serves the requested resource to the consumer
The Architecture section of the docs covers details of protecting your APIs with Envoy and Authorino, including information about topology (centralized gateway, centralized authorization service or sidecars), deployment modes (cluster-wide reconciliation vs. namespaced instances), an specification of Authorino's
AuthConfig Custom Resource Definition (CRD) and more.
You will also find in that section information about what happens in request-time (aka Authorino's Auth Pipeline) and how to leverage the Authorization JSON for writing policies, dynamic responses and other features of Authorino.
List of features
|Identity verification & authentication||JOSE/JWT validation (OpenID Connect)||Ready|
|OAuth 2.0 Token Introspection (opaque tokens)||Ready|
|Kubernetes TokenReview (SA tokens)||Ready|
|OpenShift User-echo endpoint||In analysis|
|API key authentication||Ready|
|HMAC authentication||Planned (#9)|
|Plain (resolved beforehand and injected in the payload)||Ready|
|Ad hoc external metadata fetching||OpenID Connect User Info||Ready|
|UMA-protected resource attributes||Ready|
|Policy enforcement/authorization||JSON pattern matching (e.g. JWT claims, request attributes checking)||Ready|
|OPA/Rego policies (inline and pull from registry)||Ready|
|Kubernetes SubjectAccessReview (resource and non-resource attributes)||Ready|
|Keycloak Authorization Services (UMA-compliant Authorization API)||In analysis|
|Custom responses||Festival Wristbands tokens (token normalization, Edge Authentication Architecture)||Ready|
|JSON injection (header injection, Envoy Dynamic Metadata)||Ready|
|Plain text value (header injection)||Ready|
|Custom response status code/messages (e.g. redirect)||Ready|
|Caching||OpenID Connect and User-Managed Access configs||Ready|
|JSON Web Keys (JWKs) and JSON Web Key Sets (JWKS)||Ready|
|Precompiled Rego policies||Ready|
|Sharding (lookup performance, multitenancy)||Ready|
For a detailed description of the features above, refer to the Features page.
Do I need to deploy Envoy?
Authorino is built from the ground up to work well with Envoy. It is strongly recommended that you leverage Envoy along side Authorino. That said, it is possible to use Authorino without Envoy.
Authorino implements Envoy's external authorization gRPC protocol and therefore will accept any client request that complies.
Authorino also provides a second interface for raw HTTP authorization, suitable for using with Kubernetes ValidatingWebhook and other integrations (e.g. other proxies).
The only attribute of the authorization request that is strictly required is the host name. (See Host lookup for more information.) The other attributes, such as method, path, headers, etc, might as well be required, depending on each
AuthConfig. In the case of the gRPC
CheckRequest method, the host is supplied in
Attributes.Request.Http.Host and alternatively in
Attributes.ContextExtensions["host"]. For raw HTTP authorization requests, the host must be supplied in
Host HTTP header.
Check out Kuadrant for easy-to-use Envoy and Authorino deployment & configuration for API management use-cases, using Kubernetes Custom Resources.
Is Authorino an Identity Provider (IdP)?
No, Authorino is not an Identity Provider (IdP). Neither it is an auth server of any kind, such as an OAuth2 server, an OpenID Connect (OIDC) server, a Single Sign On (SSO) server.
Authorino is not an identity broker either. It can verify access tokens from multiple trusted sources of identity and protocols, but it will not negotiate authentication flows for non-authenticated access requests. Some tricks nonetheless can be done, for example, to redirect unauthenticated users to a login page.
For an excellent auth server that checks all the boxes above, check out Keycloak.
How does Authorino compare to Keycloak?
Keycloak is a proper auth server and identity provider (IdP). It offers a huge set of features for managing identities, identity sources with multiple user federation options, and a platform for authentication and authorization services.
Keycloak exposes authenticators that implement protocols such as OpenID Connect. The is a one-time flow that establishes the delegation of power to a client, for a short period of time. To be consistent with Zero Trust security, you want a validator to verify the short-lived tokens in every request that tries to reach your protected service/resource. This step that will repeat everytime could save heavy looking up into big tables of tokens and leverage cached authorization policies for fast in-memory evaluation. This is where Authorino comes in.
Authorino verifies and validates Keycloak-issued ID tokens. OpenID Connect Discovery is used to request and cache JSON Web Key Sets (JWKS), used to verify the signature of the tokens without having to contact again with the Keycloak server, or looking in a table of credentials. Moreover, user long-lived credentials are safe, rather than spread in hops across the network.
You can also use Keycloak for storing auth-relevant resource metadata. These can be fetched by Authorino in request-time, to be combined into your authorization policies. See Keycloak Authorization Services and User-Managed Access (UMA) support, as well as Authorino UMA external metadata counter-part.
Why doesn't Authorino handle OAuth flows?
It has to do with trust. OAuth grants are supposed to be negotiated directly between whoever owns the long-lived credentials in one hand (user, service accounts), and the trustworthy auth server that receives those credentials – ideally with minimum number of hops in the middle – and exchanges them for short-lived access tokens, on the other end.
There are use-cases for Authorino running in the edge (e.g. Edge Authentication Architecture and token normalization), but in most cases Authorino should be seen as a last-mile component that provides decoupled identity verification and authorization policy enforcement to protected services in request-time. In this sense, the OAuth grant is a pre-flight exchange that happens once and as direct and safe as possible, whereas auth enforcement is kept lightweight and efficient.
Where does Authorino store users and roles?
Authorino does not store users, roles, role bindings, access control lists, or any raw authorization data. Authorino handles policies, where even these policies can be stored elsewhere (as opposed to stated inline inside of an Authorino
Authorino evaluates policies for stateless authorization requests. Any additional context is either resolved from the provided payload or static definitions inside the policies. That includes extracting user information from a JWT or client TLS certificate, requesting user metadata from opaque authentication tokens (e.g. API keys) to the trusted sources actually storing that content, obtaining synchronous HTTP metadata from services, etc.
In the case of authentication with API keys, as well as its derivative to model HTTP Basic Auth, user data are stored in Kubernetes
Secrets. The secret's keys, annotations and labels are usually the structures used to organize the data that later a policy evaluated in Authorino may require. Strictly, those are not Authorino data structures.
Can't I just use Envoy JWT Authentication and RBAC filters?
Envoy's JWT Authentication works pretty much similar to Authorino's JOSE/JWT verification and validation for OpenID Connect. In both cases, the JSON Web Key Sets (JWKS) to verify the JWTs are auto-loaded and cached to be used in request-time. Moreover, you can configure for details such as where to extract the JWT from the HTTP request (header, param or cookie) and do some cool tricks regarding how dynamic metadata based on JWT claims can be injected to consecutive filters in the chain.
However, in terms of authorization, while Envoy's implementation essentially allows to check for the list of audiences (
aud JWT claim), Authorino opens up for a lot more options such as pattern-matching rules with operators and conditionals, built-in OPA and other methods of evaluating authorization policies.
Authorino also allows to combine JWT authentication with other types of authentication to support different sources of identity and groups of users such as API keys, Kubernetes tokens, OAuth opaque tokens , etc.
In summary, Envoy's JWT Authentication and Envoy RBAC filter are excellent solutions for simple use-cases where JWTs from one single issuer is the only authentication method you are planning to support and limited to no authorization rules suffice. On the other hand, if you need to integrate more identity sources, different types of authentication, authorization policies, etc, you might to consider Authorino.
Should I use Authorino if I already have Istio configured?
Istio is a great solution for managing service meshes. It delivers an excellent platform with an interesting layer of abstraction on top of Envoy proxy's virtual omnipresence within the mesh.
There are lots of similarities, but also complementarity between Authorino and Istio and Istio Authorization in special.
Istio provides a simple way to enable features that are, in many cases, features of Envoy, such as authorization based on JWTs, authorization based on attributes of the request, and activation of external authorization services, without having to deal with complex Envoy config files. See Kuadrant for a similar approach, nonetheless leveraging features of Istio as well.
Authorino is an Envoy-compatible external authorization service. One can use Authorino with or without Istio.
In particular, Istio Authorization Policies can be seen, in terms of functionality and expressiveness, as a subset of one type of authorization policies supported by Authorino, the pattern-matching authorization policies. While Istio, however, is heavily focused on specific use cases of API Management, offering a relatively limited list of supported attribute conditions, Authorino is more generic, allowing to express authorization rules for a wider spectrum of use cases – ACLs, RBAC, ABAC, etc, pretty much counting on any attribute of the Envoy payload, identity object and external metadata available.
Authorino also provides built-in OPA authorization, several other methods of authentication and identity verification (e.g. Kubernetes token validation, API key-based authentication, OAuth token introspection, OIDC-discoverable JWT verification, etc), and features like fetching of external metadata (HTTP services, OIDC userinfo, UMA resource data), token normalization, wristband tokens and dynamic responses. These all can be used independently or combined, in a simple and straightforward Kubernetes-native fashion.
In summary, one might value Authorino when looking for a policy enforcer that offers:
- multiple supported methods and protocols for rather hybrid authentication, encompassing future and legacy auth needs;
- broader expressiveness and more functionalities for the authorization rules;
- authentication and authorization in one single declarative manifest;
- capability to fetch auth metadata from external sources on-the-fly;
- built-in OPA module;
- easy token normalization and/or aiming for Edge Authentication Architecture (EAA).
The good news is that, if you have Istio configured, then you have Envoy and the whole platform for wiring Authorino up if you want to. 😉
Do I have to learn OPA/Rego language to use Authorino?
No, you do not. However, if you are comfortable with Rego from Open Policy Agent (OPA), there are some quite interesting things you can do in Authorino, just as you would in any OPA server or OPA plugin, but leveraging Authorino's built-in OPA module instead. Authorino's OPA module is compiled as part of Authorino's code directly from the Golang packages, and imposes no extra latency to the evaluation of your authorization policies. Even the policies themselves are pre-compiled in reconciliation-time, for fast evaluation afterwards, in request-time.
On the other hand, if you do not want to learn Rego or in any case would like to combine it with declarative and Kubernetes-native authN/authZ spec for your services, Authorino does complement OPA with at least two other methods for expressing authorization policies – i.e. pattern-matching authorization and Kubernetes SubjectAccessReview, the latter allowing to rely completely on the Kubernetes RBAC.
You break down, mix and combine these methods and technolgies in as many authorization policies as you want, potentially applying them according to specific conditions. Authorino will trigger the evaluation of concurrent policies in parallel, aborting the context if any of the processes denies access.
Authorino also packages well-established industry standards and protocols for identity verification (JOSE/JWT validation, OAuth token introspection, Kubernetes TokenReview) and ad-hoc request-time metadata fetching (OIDC userinfo, User-Managed Access (UMA)), and corresponding layers of caching, without which such functionalities would have to be implemented by code.
Can I use Authorino to protect non-REST APIs?
Yes, you can. In principle, the API format (REST, gRPC, GraphQL, etc) should not matter for the authN/authZ enforcer. There are a couple points to consider though.
While REST APIs are designed in a way that, in most cases, information usually needed for the evaluation of authorization policies are available in the metadata of the HTTP request (method, path, headers), other API formats quite often will require processing of the HTTP body. By default, Envoy's external authorization HTTP filter will not forward the body of the request to Authorino; to change that, enable the
with_request_body option in the Envoy configuration for the external authorization filter. E.g.:
Additionally, when enabling the request body passed in the payload to Authorino, parsing of the content should be of concern as well. Authorino provides easy access to attributes of the HTTP request, parsed as part of the Authorization JSON, however the body of the request is passed as string and should be parsed by the user according to each case.
Check out Authorino OPA authorization and the Rego Encoding functions for options to parse serialized JSON, YAML and URL-encoded params. For XML transformation, an external parsing service connected via Authorino's HTTP GET/GET-by-POST external metadata might be required.
Can I run Authorino other than on Kubernetes?
As of today, no, you cannot, or at least it wouldn't suit production requirements.
Do I have to be admin of the cluster to install Authorino?
To install the Authorino Custom Resource Definition (CRD) and to define cluster roles required by the Authorino service, admin privilege to the Kubernetes cluster is required. This step happens only once per cluster and is usually equivalent to installing the Authorino Operator.
Thereafter, deploying instances of the Authorino service and applying
AuthConfig custom resources to a namespace depend on the permissions set by the cluster administrator – either directly by editing the bindings in the cluster's RBAC, or via options of the operator. In most cases, developers will be granted permissions to create and manage
AuthConfigs, and sometimes to deploy their own instances of Authorino.
Is it OK to store AuthN/AuthZ configs as Kubernetes objects?
Authorino's API checks all the bullets to be aggregated to the Kubernetes cluster APIs, and therefore using Custom Resource Definition (CRD) and the Operator pattern has always been an easy design decision.
By merging the definitions of service authN/authZ to the control plane, Authorino
AuthConfig resources can be thought as extensions of the specs of the desired state of services regarding the data flow security. The Authorino custom controllers, built-in into the authorization service, are the agents that read from that desired state and reconcile the processes operating in the data plane.
Authorino is declarative and seamless for developers and cluster administrators managing the state of security of the applications running in the server, used to tools such as
kubectl, the Kubernetes UI and its dashboards. Instead of learning about yet another configuration API format, Authorino users can jump straight to applying and editing YAML or JSON structures they already know, in a way that things such as
labels have the meaning they are expected to have, and docs are as close as
kubectl explain. Moreover, Authorino does not pile up any other redundant layers of APIs, event-processing, RBAC, transformation and validation webhooks, etc. It is Kubernetes in its best.
In terms of scale, Authorino
AuthConfigs should grow proportionally to the number of protected services, virtually limited by nothing but the Kubernetes API data storage, while namespace division and label selectors help adjust horizontally and keep distributed.
In other words, there are lots of benefits of using Kubernetes custom resources and custom controllers, and unless you are planning on bursting your server with more services than it can keep record, it is totally 👍 to store your AuthN/AuthZ configs as cluster API objects.
Can I use Authorino for rate limiting?
You can, but you shouldn't. Check out instead Limitador, for simple and efficient global rate limiting. Combine it with Authorino and Authorino's support for Envoy Dynamic Metadata for authenticated rate limiting.
Configuration of the tests (Authorino features):
(JWT claim check)
CPU: Intel® Xeon® Platinum 8370C 2.80GHz
Cores: 1, 4, 10
ReconcileAuthConfig: │ sec/op │ B/op │ allocs/op │ * 1.533m ± 2% 264.4Ki ± 0% 6.470k ± 0% *-4 1.381m ± 6% 264.5Ki ± 0% 6.471k ± 0% *-10 1.563m ± 5% 270.2Ki ± 0% 6.426k ± 0% geomean 1.491m 266.4Ki 6.456k AuthPipeline: │ sec/op │ B/op │ allocs/op │ * 388.0µ ± 2% 80.70Ki ± 0% 894.0 ± 0% *-4 348.4µ ± 5% 80.67Ki ± 2% 894.0 ± 3% *-10 356.4µ ± 2% 78.97Ki ± 0% 860.0 ± 0% geomean 363.9µ 80.11Ki 882.5 APIKeyAuthn: │ sec/op │ B/op │ allocs/op │ * 3.246µ ± 1% 480.0 ± 0% 6.000 ± 0% *-4 3.111µ ± 0% 480.0 ± 0% 6.000 ± 0% *-10 3.091µ ± 1% 480.0 ± 0% 6.000 ± 0% geomean 3.148µ 480.0 6.000 OPAAuthz vs JSONPatternMatchingAuthz: │ OPAAuthz │ JSONPatternMatchingAuthz │ │ sec/op │ sec/op vs base │ * 87.469µ ± 1% 1.797µ ± 1% -97.95% (p=0.000 n=10) *-4 95.954µ ± 3% 1.766µ ± 0% -98.16% (p=0.000 n=10) *-10 96.789µ ± 4% 1.763µ ± 0% -98.18% (p=0.000 n=10) geomean 93.31µ 1.775µ -98.10% │ OPAAuthz │ JSONPatternMatchingAuthz │ │ B/op │ B/op vs base │ * 28826.00 ± 0% 64.00 ± 0% -99.78% (p=0.000 n=10) *-4 28844.00 ± 0% 64.00 ± 0% -99.78% (p=0.000 n=10) *-10 28862.00 ± 0% 64.00 ± 0% -99.78% (p=0.000 n=10) geomean 28.17Ki 64.00 -99.78% │ OPAAuthz │ JSONPatternMatchingAuthz │ │ allocs/op │ allocs/op vs base │ * 569.000 ± 0% 2.000 ± 0% -99.65% (p=0.000 n=10) *-4 569.000 ± 0% 2.000 ± 0% -99.65% (p=0.000 n=10) *-10 569.000 ± 0% 2.000 ± 0% -99.65% (p=0.000 n=10) geomean 569.0 2.000 -99.65%
If you are interested in contributing to Authorino, please refer to the Developer's guide for info about the stack and requirements, workflow, policies and Code of Conduct.
Join us on the #kuadrant channel in the Kubernetes Slack workspace, for live discussions about the roadmap and more.