7.3

Table Of Contents
REST API Authentication 2
In the REST API, vRealize Automation requires HTTP bearer tokens in request headers for authentication
of consumer requests. A consumer request applies to tasks that you can perform in the
vRealize Automation console, such as requesting a machine.
To acquire an HTTP bearer token, you authenticate with an identity service that manages the
communication with the SSO server. The identity service returns an HTTP bearer token that you include
in all request headers until the token expires, or you delete it. An HTTP bearer token expires in 24 hours
by default, but you can configure the token with a different duration.
This chapter includes the following topics:
n
About HTTP Bearer Tokens
n
Configure the Duration of an HTTP Bearer Token
n
Request an HTTP Bearer Token
n
Validate an HTTP Bearer Token
n
Delete an HTTP Bearer Token
About HTTP Bearer Tokens
You use HTTP bearer tokens for tasks that you can also perform in the vRealize Automation console. You
create a request header with the curl command or with some other utility.
You use POST, HEAD, and DELETE methods to manage HTTP bearer tokens.
Method URL Description
POST /tokens Authenticate the user with the identity service /tokens and
generate a new token.
HEAD /tokens/tokenID Validate the token tokenID.
DELETE /tokens/tokenID Delete the token tokenID.
Use the following root URL for HTTP bearer token calls:
https://$vRA/identity/api/tokens
The variable $vRA represents the appliance name.domain name of the vRealize Automation server
such as, vra-appliance-name.company.com.
VMware, Inc.
13