Clarify capability lists should support wildcards

This commit is contained in:
Tom Foster 2025-02-14 15:00:53 +00:00
parent 1cc93ec951
commit 0b0942d192

View file

@ -154,13 +154,10 @@ components:
type: object type: object
title: ProfileFieldsCapability title: ProfileFieldsCapability
properties: properties:
enabled:
type: boolean
description: True if the user can set or modify any extended profile fields, false otherwise.
example: true
allowed: allowed:
type: array type: array
description: List of allowed custom profile field keys. This takes precedence over disallowed if both are provided. description: List of allowed custom profile field keys,
supporting `glob.*` wildcard format. Takes precedence over disallowed if both are provided.
items: items:
type: string type: string
example: example:
@ -168,10 +165,15 @@ components:
- "org.example.job_title" - "org.example.job_title"
disallowed: disallowed:
type: array type: array
description: List of disallowed custom profile field keys. Ignored if allowed is provided. description: List of disallowed custom profile field keys,
supporting `glob.*` wildcard format. Ignored if allowed is provided.
items: items:
type: string type: string
example: example:
- "org.example.secret_field" - "org.example.secret_field"
enabled:
type: boolean
description: True if the user can set or modify any extended profile fields, false otherwise.
example: true
required: required:
- enabled - enabled