Re: Attribute Array in JSON Request

Hi,

In retrospect, I think I probably forgot. The profile is inconsistent in how I handle arrays. That said, now that I attempted to write a swagger definition, I realize that shortcuts like allowing an array to be a single-valued object does not save you much and makes your code much harder.

Did anyone get a chance to try the swagger I wrote?

Thanks

On Thu, Feb 1, 2018 at 4:45 PM, Steven Legg <steven.legg@viewds.com> wrote:

Hi David,

Cyril's review comments on the JSON profile call out the Attribute field in
the Action object in the example request in Section 8.1 as being in error because
it is not an array of objects. I'm not so sure that is the error. You have various
cases where fields that may take multiple values may be represented as a single
object instead of an array containing a single object. Did you intend that this
rule should also apply to the Attribute field but didn't make it explicit, or
did you intend that the Attribute field always be an array?

Regards,
Steven

David Brossard
VP of Customer Relations

+1 312 774-9163

+1 502 922 6538

+46(0)760 25 85 75

Axiomatics | 525 W. Monroe Suite 2310 | Chicago 60661

Support: https://support.axiomatics.com
Web: http://www.axiomatics.com

Axiomatics Blog | Events | Resources, Webinars & Whitepapers

Connect with us on LinkedIn | Twitter | Google + | Facebook | YouTube

xacml-comment message