Difference between revisions of "Keystone"
| Line 58: | Line 58: | ||
* [[KeystoneUseCases]] | * [[KeystoneUseCases]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 04:25, 16 November 2012
OpenStack Identity ("Keystone")
| Source code |
| Bug tracker |
| Blueprints |
| Developer doc |
Related projects
- Python Keystone client
- Identity API documentation
Documentation
What is Keystone?
Keystone is the identity service used by OpenStack for authentication (authN) and high-level authorization (authZ). It currently supports token-based authN and user-service authorization. It has recently been rearchitected to allow for expansion to support proxying external services and AuthN/AuthZ mechanisms such as oAuth, SAML and openID in future versions.
Meetings
Doc
Code
- Source
- Pending Code Reviews:
Bugs and Blueprints
- keystone bugs
- keystone client bugs
- blueprints
- bugs tags
- blueprint (implies bug indicates a needed feature or function, can be migrated to a blueprint)
- python-keystoneclient (related to the client end of keystone)
- legacy (existing prior to the feb14, 2012 rebaseline of the code)
- gsoc (appropriate for a google summer of code project effort)
- low-hanging-fruit (easy piece for someone to get started with, minimal design needed to solve)
- importance meanings
- critical (bug renders the system non-functional)
- high (bug we want resolved before the next release)
- medium/low (general issue bug or annoyance, perhaps requiring significant design change to implement or new features needed to resolve)
- wishlist (nice to have)
Use Cases
