The Identity of OpenStack, Keystone

Keystone, the heart of OpenStack's Identity

Authentication, Authorization is the starting point of API call. IAM in AWS, GCP, or Azure is core component for Authentication and Authorization. In the OpenStack, keystone works as IAM.

I want to understand how keystone works?

The basic concept of Authentication, Authorization in the micro service architecture is 1) there is a central identity which publishs token, 2) all other micro services validate token(authentication) and check permission (authorization)

Keystone v2 and v3

Keystone v3 supports Domain and Project

Token Types

Type	Description	Support From
UUID	32-bit UUID, Just random number
FERNET	256Bytes, symmetric encryption and signing	Kilo (default since Queens)
JWS	JSON Web Token, asymmetric cryptography	Stein

Fernet and JWS has no databased backed

UUID

[token]
provider = keystone.token.providers.uuid.Provider

FERNET (Cryptographic Authentication Method)

[token]
provider = keystone.token.providers.fernet.Provider
[fernet_tokens]
key_repository = /etc/keystone/fernet-keys/
max_active_keys = <number of keys> # defaults is 3

JWS (JSON Web Signature)

a type of JWT (JSON Web Token)

[token]
provider = jws
[jwt_tokens]
jws_public_key_repository = /etc/keystone/jws-keys/public
jws_private_key_repository = /etc/keystone/jws-keys/private

Token Scope

Type	Description
Un-scoped	-
System	interacting with resources at the system level, usually admin only
Domain	Users and Groups
Project	users to work on items that fit withinn a project scope