Date: Thu, 28 Mar 2024 15:44:35 +0000 (UTC) Message-ID: <456395826.6595.1711640675928@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6594_1943730771.1711640675927" ------=_Part_6594_1943730771.1711640675927 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Get permission assignments. These permissions can be on roles or s= ubjects (note if assignment is assigned directly to a subject, it is in the= context of a role).
You can lookup permissions by attribute definition, attribute definition= name, role name or uuid, or subject. You can filter by action. Note = you must pass in at least an attribute definition, attribute definition nam= e, role, or subject, and you can mix and match.
All returned permission assignments will be filtered for security based = on the logged in or acted as user (security rules are on attribute framework wiki)
The returned data will include the permission assignments, and a normali= zed list of references (role, attribute definitions, attribute names (if re= quested with includeAttributeDefNames=3DT), subjects, etc)
You can lookup assignments by multiple owners, definitions, subjects, ac= tions, etc (non-lite operation only)
If you want to return details on the assignment (e.g. the depth of each = hierarchy etc), pass in the param: includePermissionAssignDetail=3DT
If you want to return the underlying attribute assignment objects, pass = in the param: includeAttributeAssignments=3DT
If there are limits or other metadata on the permission, to read those, = pass in includeAttributeAssignments=3DT and includeAssignmentsOnAssignments= =3DT. Note these attribute assignments on assignments are only on the immed= iate assignment, not effective.