E1: AIS: What Is "aisSessionCookie" and "userAuthorized" In JSON Response For Token Request? (Doc ID 2522201.1)

Last updated on AUGUST 29, 2022

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Goal

Question 1. In an AIS token request, what is the returned value "aisSessionCookie"? When making restful call to AIS for token request at end point ".../tokenrequest" what is the significant of the response JSON object "aisSessionCookie"? How does this aisSessionCookie affect subsequent AIS calls using the same token?

Question 2. In an AIS token request response what ""userAuthorized" : false" means in response?

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Question 1. In an AIS token request, what is the returned value "aisSessionCookie"? When making restful call to AIS for token request at end point ".../tokenrequest" what is the significant of the response JSON object "aisSessionCookie"? How does this aisSessionCookie affect subsequent AIS calls using the same token?

Question 2. In an AIS token request response what ""userAuthorized" : false" means in response?

Answer 1. The session cookie is just re-iterating the cookie that gets set in the header response from a login request. There’s no specific use case for the cookie in the body. The use case for the header cookie is for clustered AIS server. The header cookie must be used for “stickiness” so that the inbound calls are always routed to the same AIS instance where they established a session within the cluster.

Answer 2. The "userAuthorized" response flag is used by mobile apps to authorize to a mobile app using Mobile app security. It is not being used with any functions within AIS or Orchestration

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.