Use of Cookies and Browser Memory

smart.finder uses cookies and browser memory (Local Storage and Session Storage) to store data over multiple browser sessions. This page provides information about which data is stored.

Browser storage (Local Storage / Session Storage)

The following list shows which bundles store data in the browser memory. Only those bundles are considered that are included in a delivery by default.

bundle description trigger

bundle	description	trigger
`esri`	ArcGIS Maps SDK for JavaScript uses the browser’s session storage to store one-time passwords which have to be randomly generated and cached when authenticating via OAuth protocol.	Authentication of the user is done via OAuth protocol to ArcGIS Online/ArcGIS Enterprise portal.
`system`	Stores the time of the last usage of the application in the local storage to be able to log out users automatically after a certain period of time.	use of smart.finder.

esri

ArcGIS Maps SDK for JavaScript uses the browser’s session storage to store one-time passwords which have to be randomly generated and cached when authenticating via OAuth protocol.

Authentication of the user is done via OAuth protocol to ArcGIS Online/ArcGIS Enterprise portal.

system

Stores the time of the last usage of the application in the local storage to be able to log out users automatically after a certain period of time.

use of smart.finder.

Cookies

At this point only cookies written by smart.finder itself are considered.The names of the cookies are configurable and can therefore differ at runtime.

Cookies are used in smart.finder to be able to assign users over a session after successful login. Which cookies are used depends on the authentication mode:

In integrated authentication mode sessions are managed by Tomcat. When a new session is created, a cookie named JSESSIONID (name may differ see above) is sent to the browser.
If authentication is done using con terra Technologies Identity Service at an external identity provider, an ctIDENTITY cookie (name possibly different see above) is written.
If the security.manager - Enterprise Edition is used for authentication, an ct_SSO cookie (name may differ, see above) is written to realize domain-wide single sign-on.