Questo contenuto non è disponibile nella lingua selezionata.
2.3. Authentication Sessions
		The API also provides the ability for authentication session support. An API user sends an initial request with authentication details, then sends all subsequent requests using a session cookie to authenticate. The following procedure demonstrates how to use an authenticated session.
	
Procedure 2.3. Requesting an authenticated session
- Send a request with theAuthorizationandPrefer: persistent-authCopy to Clipboard Copied! Toggle word wrap Toggle overflow This returns a response with the following header:Set-Cookie: JSESSIONID=5dQja5ubr4yvI2MM2z+LZxrK; Path=/ovirt-engine/api; Secure Set-Cookie: JSESSIONID=5dQja5ubr4yvI2MM2z+LZxrK; Path=/ovirt-engine/api; SecureCopy to Clipboard Copied! Toggle word wrap Toggle overflow Note theJSESSIONID=value. In this example the value isJSESSIONID=5dQja5ubr4yvI2MM2z+LZxrK.
- Send all subsequent requests with thePrefer: persistent-authandcookieheader with theJSESSIONID=value. TheAuthorizationis no longer needed when using an authenticated session.Copy to Clipboard Copied! Toggle word wrap Toggle overflow 
- When the session is no longer required, perform a request to the sever without thePrefer: persistent-authheader.Copy to Clipboard Copied! Toggle word wrap Toggle overflow