Athenz is a set of services and libraries supporting service authentication and role-based authorization (RBAC) for provisioning and configuration (centralized authorization) use cases as well as serving/runtime (decentralized authorization) use cases. Athenz authorization system utilizes x.509 certificates and two types of tokens: Principal Tokens (N-Tokens) and RoleTokens (Z-Tokens). The use of x.509 certificates is strongly recommended over tokens. The name "Athenz" is derived from "AuthNZ" (N for authentication and Z for authorization).

• Background
• Install
• Usage
• Contribute
• License

Athenz is an open source platform for X.509 certificate based service authentication and fine grained role based access control in dynamic infrastructures. It provides support for the following three major functional areas.

Athenz provides secure identity in the form of short lived X.509 certificate for every workload or service deployed in private (e.g. Openstack, K8S, Screwdriver) or public cloud (e.g. AWS EC2, ECS, Fargate, Lambda). Using these X.509 certificates clients and services establish secure connections and through mutual TLS authentication verify each other's identity. The service identity certificates are valid for 30 days only and the service identity agents (SIA) part of those frameworks automatically refresh them daily. The term service within Athenz is more generic than a traditional service. A service identity could represent a command, job, daemon, workflow, as well as both an application client and an application service.

Since Athenz service authentication is based on X.509 certificates, it is important that you have a good understanding what X.509 certificates are and how they're used to establish secure connections in Internet protocols such as TLS.

Once the client is authenticated with its x.509 certificate, the service can then check if the given client is authorized to carry out the requested action. Athenz provides fine-grained role-based access control (RBAC) support for a centralized management system with support for control-plane access control decisions and a decentralized enforcement mechanism suitable for data-plane access control decisions. It also provides a delegated management model that supports multi-tenant and self-service concepts.

When working with AWS, Athenz provides support to access AWS services from on-prem services with using AWS temporary credentials rather than static credentials. Athenz ZTS server can be used to request AWS temporary credentials for configured AWS IAM roles.

• Development Environment
• Local/Development Environment Setup
  • ZMS Server
  • ZTS Server
  • UI Server
• Production Environment Setup
  • ZMS Server
  • ZTS Server
  • UI Server
• AWS Production Environment Setup
  • Introduction
  • ZMS Server
  • ZTS Server
  • UI Server

• Architecture
  • Data Model
  • System View
  • Authorization Flow
• Features
  • Service Identity X.509 Certificates - Copper Argos
• Developer Guide
  • Centralized Access Control
    • Java Client/Servlet Example
    • Go Client/Server Example
  • Decentralized Access Control
    • Java Client/Servlet Example
• Customizing Athenz
  • Principal Authentication
  • Private Key Store
  • Certificate Signer
  • Service Identity X.509 Certificate Support Requirements - Copper Argos
• User Guide
  • ZMS Client Utility
  • ZPU Utility
  • Registering ZMS Service Identity
  • ZMS API
  • ZTS API

Please refer to the contributing file for information about how to get involved. We welcome issues, questions, and pull requests.

You can also contact us for any user and development discussions through our groups:

• Athenz-Dev for development discussions
• Athenz-Users for users questions

Copyright 2016 Yahoo Inc.

Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0