One of the most impactful decisions you’ll have to make when configuring keystone is deciding how you want keystone to source your identity data. Keystone supports several different choices that will substantially impact how you’ll configure, deploy, and interact with keystone.
You can also mix-and-match various sources of identity (see Domain-specific Configuration for an example). For example, you can store OpenStack service users and their passwords in SQL, manage customers in LDAP, and authenticate employees via SAML federation.
Summary
Feature | Status | LDAP | OAuth v1.0a | OpenID Connect | REMOTE_USER | SAML v2 | SQL |
---|---|---|---|---|---|---|---|
Local authentication | optional | ✔ |
✔ |
✖ |
✖ |
✖ |
✔ |
External authentication | optional | ✖ |
✖ |
✔ |
✔ |
✔ |
✖ |
Identity management | optional | ✔ |
✔ |
✖ |
✖ |
✖ |
✔ |
PCI-DSS controls | optional | ✔ |
✖ |
✖ |
✔ |
✖ |
✔ |
Auditing | optional | ✔ |
✖ |
✔ |
✖ |
✔ |
✔ |
Details
Status: optional.
Notes: Authenticate with keystone by providing credentials directly to keystone.
Driver Support:
complete
complete
missing
missing
missing
complete
Status: optional.
Notes: Authenticate with keystone by providing credentials to an external system that keystone trusts (as with federation).
Driver Support:
missing
missing
complete
complete
complete
missing
Status: optional.
Notes: Create, update, enable/disable, and delete users via Keystone’s HTTP API.
Driver Support:
partial
complete
missing
missing
missing
complete
Status: optional.
Notes: Configure keystone to enforce PCI-DSS compliant security controls.
Driver Support:
partial
missing
missing
partial
missing
complete
Status: optional.
Notes: Audit authentication flows using PyCADF.
Driver Support:
complete
missing
complete
missing
complete
complete
Notes:
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.