601eeb50b6
Blueprint trusts creates a trust. Using a trust, one user (the trustee), can then create tokens with a subset of another user's (the trustor) roles and projects. If the impersonate flag in the trust is set, the token user_id is set to the trustor's user ID If the impersonate flag is not set, the token's user_is is set to the trustee's user ID check that both trustor and trustee are enabled prior to creating the trust token. sql and kvs backends sql upgrade scripts unit tests for backends, auth and v3 api modifications to the trust controller for creating tokens Authenticates that only user can be trustor in create Deleting a trust invalidates all tokens created from that trust Adds the trust id and the id of the trustee to the header of the token policy rules for trust This version has a workaround for testing against the KVS version of the Service catalog Change-Id: I5745f4d9a4180b59671a143a55ed87019e98ec76
18 lines
415 B
Plaintext
18 lines
415 B
Plaintext
[DEFAULT]
|
|
crypt_strength = 1000
|
|
|
|
[identity]
|
|
driver = keystone.identity.backends.kvs.Identity
|
|
|
|
[catalog]
|
|
driver = keystone.catalog.backends.templated.TemplatedCatalog
|
|
template_file = default_catalog.templates
|
|
|
|
[trust]
|
|
driver = keystone.trust.backends.kvs.Trust
|
|
|
|
[signing]
|
|
certfile = ../examples/pki/certs/signing_cert.pem
|
|
keyfile = ../examples/pki/private/signing_key.pem
|
|
ca_certs = ../examples/pki/certs/cacert.pem
|