Azure Key Vault: Rbac
The key vault client performs cryptographic key operations and vault operations against the Key Vault service.
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
The key vault client performs cryptographic key operations and vault operations against the Key Vault service.
Endpoints 8
RoleDefinitions
- GETRoleDefinitions_Get
/:scope/providers/Microsoft.Authorization/roleDefinitions/:roleDefinitionNameGet the specified role definition. - PUTRoleDefinitions_CreateOrUpdate
/:scope/providers/Microsoft.Authorization/roleDefinitions/:roleDefinitionNameCreates or updates a custom role definition. - DELETERoleDefinitions_Delete
/:scope/providers/Microsoft.Authorization/roleDefinitions/:roleDefinitionNameDeletes a custom role definition. - GETRoleDefinitions_List
/:scope/providers/Microsoft.Authorization/roleDefinitions?$filter=stringGet all role definitions that are applicable at scope and above.
RoleAssignments
- GETRoleAssignments_Get
/:scope/providers/Microsoft.Authorization/roleAssignments/:roleAssignmentNameGet the specified role assignment. - PUTRoleAssignments_Create
/:scope/providers/Microsoft.Authorization/roleAssignments/:roleAssignmentNameCreates a role assignment. - DELETERoleAssignments_Delete
/:scope/providers/Microsoft.Authorization/roleAssignments/:roleAssignmentNameDeletes a role assignment. - GETRoleAssignments_ListForScope
/:scope/providers/Microsoft.Authorization/roleAssignments?$filter=stringGets role assignments for a scope.
API details
- Authentication
- None declared in the description
- Operations
- 8 operations on 4 pathsGET 4PUT 2DELETE 2
- Main resources
- RoleAssignments 4RoleDefinitions 4
- Response formats
application/json- Description format
- Swagger 2.0, API version
7.4 - Links
- OpenAPI document
How to test the Azure Key Vault: Rbac in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Azure Key Vault: Rbac collection, without the publisher's secrets.
- Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
- Send a requestPick an endpoint, for example “RoleDefinitions_Get” (GET /:scope/providers/Microsoft.Authorization/roleDefinitions/:roleDefinitionName), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Azure Key Vault: Rbac?
The key vault client performs cryptographic key operations and vault operations against the Key Vault service. It is listed under Identity & security and has 8 endpoints.
Who publishes the Azure Key Vault: Rbac?
It is listed from Microsoft Azure's public API description (an OpenAPI document), not published by Microsoft Azure on Swastik Codes. Anyone who controls azure.com can claim the profile by adding a DNS TXT record.
How do I authenticate with the Azure Key Vault: Rbac?
Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.
How many endpoints does the Azure Key Vault: Rbac have?
8 operations on 4 paths (4 GET, 2 PUT, 2 DELETE). The largest groups are RoleAssignments, RoleDefinitions.
Is forking the Azure Key Vault: Rbac free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.