Find Permission Attributes

post

/access-governance/service-administration/20250331/orchestratedSystems/{orchestratedSystemId}/permissionAttributes

Returns metadata and a set of permissions associated with a given orchestrated system.

Request

Path Parameters
Header Parameters
  • The client request ID for tracing. The only valid characters for request IDs are letters, numbers, underscore, and dash.
Body ()
List of Permissions used to find attributes
Root Schema : OrchestratedSystemPermissionIdCollection
Type: object
A list of permission ids used to obtain a list of permission attributes.
Show Source
Nested Schema : items
Type: array
List of permission ids.
Show Source
Nested Schema : OrchestratedSystemPermissionId
Type: object
Id of permission
Show Source
Back to Top

Response

Supported Media Types

200 Response

Permission Attributes Metadata
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : OrchestratedSystemAttributes
Type: object
The information about Orchestrated System attributes metadata
Show Source
Nested Schema : items
Type: array
collection of account & permission attributes
Show Source
Nested Schema : OrchestratedSystemAttribute
Type: object
Account & permission attributes
Show Source
Nested Schema : accountAttributes
Type: array
List of Orchestrated System account attributes
Show Source
Nested Schema : Info
Type: object
Generic information object.
Show Source
Nested Schema : permissionAttributes
Type: array
List of Orchestrated System permission attributes
Show Source
Nested Schema : OrchestratedSystemAttributeData
Type: object
Orchestrated System Attributes
Show Source
Nested Schema : children
Type: array
nested attributes
Show Source
Nested Schema : defaultValues
Type: array
Attribute Value
Show Source
Nested Schema : NestedAttributes
Type: object
Nested set of Orchestrated System attributes
Show Source
Nested Schema : items
Type: array
Orchestrated System attributes
Show Source

400 Response

Bad Request
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error Information.
Show Source

401 Response

Unauthorized
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error Information.
Show Source

404 Response

Not Found
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error Information.
Show Source

409 Response

Conflict
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error Information.
Show Source

429 Response

Too Many Requests
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error Information.
Show Source

500 Response

Internal Server Error
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error Information.
Show Source

Default Response

Unknown Error
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error Information.
Show Source
Back to Top

Examples

The following example shows how to retrieve permission attributes metadata by submitting a POST request. For example, you need this data for creating an access bundle. Replace placeholder values with actual values before running the sample command.

cURL Request Example

curl -i -X POST \
   -H "Authorization:Bearer <your access token>" \
   -H "Content-Type:application/json" \
   -d \
'{
    "items": [
       {
	"id": "privileges.ICF.da7efca4-8c7a-4d4f-8ad3-xxxxxxx27642f31e6ccda",
         "name": "ADMINISTER ANY SQL TUNING SET"
       },
         {
         "id": "privileges.ICF.da7efca4-8c7a-4d4f-8ad3-c55ac9362de6.xxxxxxxx51f96ab2f305cc7f11",
		"name": "ADMINISTER DATABASE TRIGGER"
       }]
}' \
 '${service-instance-url}/access-governance/service-administration/${versionID}/orchestratedSystems/${orchestratedSystemId}/permissionAttributes'

Example Request Payload

In your REST Client tool, submit the POST request
${service-instance-url}/access-governance/service-administration/${versionID}/orchestratedSystems/${orchestratedSystemId}/permissionAttributes
{
"items": [
       {
	"id": "privileges.ICF.da7efca4-8c7a-4d4f-8ad3-xxxxxxx27642f31e6ccda",
         "name": "ADMINISTER ANY SQL TUNING SET"
       },
         {
         "id": "privileges.ICF.da7efca4-8c7a-4d4f-8ad3-c55ac9362de6.xxxxxxxx51f96ab2f305cc7f11",
		"name": "ADMINISTER DATABASE TRIGGER"
       }
]
}

Example of the Response Code

You'll receive 200 OK response along with the following response body:

{
    "items": [
        {
            "orchestratedSystem": {
                "id": "bdxxff2a-xcxx-xxxx-xxxx-9baxxxfbbxec",
                "name": null,
                "displayName": null
            },
            "accountAttributes": null,
            "permissionAttributes": [
                {
                    "name": "groups.ICF.exaaxfxx-9eed-4a25-b8cc-a04c3fbxdxxa.xxde257cb525e0df8afxxxdxxxxxxe0",
                    "type": null,
                    "title": null,
                    "children": [
                    ],
                    "lookupType": null,
                    "permissionType": "__uid__",
                    "discriminator": null,
                    "defaultValues":[]
                }
            ]
        }
    ]
}
Back to Top