Kong Identity uses principals and directories to unify how Kong products represent the entities they authenticate.
- Principal: Represents an external client, workload, or human authenticating to a Kong Gateway (not a Konnect user or Dev Portal developer).
- Directory: Regional collection of principals. Each Konnect organization can provision up to one directory per region by default.
Principals work with:
- Kong Gateway in Konnect: Principals can authenticate an entity for API traffic (using API keys or basic auth usernames and passwords), or can provide metadata about an entity already authenticated through another mechanism (for example, OAuth).
- Event Gateway: Principals can provide metadata about an entity already authenticated through another mechanism (for example, SASL/SCRAM or SASL/OAUTHBEARER).
- Dev Portal: Principals can adjust API gateway behavior based on the authenticating Dev Portal.
A directory is the organizational boundary for grouping principals and managing their identities. Directories are region-specific, and each directory controls which control planes can make authentication requests to it.