;ve also considered building a single nested JSON
document and serializing that into the 'blob' section of the 'policy'
attribute.
Our service is not an Openstack service, so we cannot take advantage
of writing policy to handle fine grained authorization of the APIs we're
much for your time and consideration,
-PG
-Original Message-
From: Phillip Guerin
Sent: Thursday, May 15, 2014 4:16 PM
To: 'openstack@lists.openstack.org'
Subject: [Openstack] [Keystone] Extending Keystone JSON documents with custom
attributes, safe?
Hello,
We're worki
I've posted to this list a couple times with some questions but I don't
see my own posts in my inbox. Is there a hold-back or review period
I should expect before my questions are posted to the list, or is this
simply configured not to send to the author?
Thanks for your time,
Phil
I've posted to this list a couple times with some questions but I
don't see my own posts in my inbox. Is there a hold-back or
review period I should expect before my questions are posted
to the list, or is this simply configured not to send to the author?
Thanks for your time,
Phil
much for your time, help, and consideration,
-PG
-Original Message-
From: Phillip Guerin
Sent: Thursday, May 15, 2014 4:16 PM
To: 'openstack@lists.openstack.org'
Subject: [Openstack] [Keystone] Extending Keystone JSON documents with custom
attributes, safe?
Hello,
We're
Are there any best practices defined around extending the Keystone JSON
documents,
or is there a better source to go to in order to get some guidance on this?
Thanks again for your time,
-PG
-Original Message-
From: Phillip Guerin [mailto:pgue...@sandvine.com]
Sent: Thursday, May 22
