This website uses cookies (small text files placed on your device) and similar technologies to provide our website and to help collect data. The text in a cookie often consists of a string of numbers and letters that uniquely identifies your computer, but it may contain other information as well.
Our Use of Cookies and Similar Technologies.
This website uses cookies and similar technologies for several purposes, which may include:
Sign-in and Authentication. When you sign into our website using your credentials, we store a unique ID number, and the time you signed in, in an encrypted cookie on your device. This cookie allows you to move from page to page within the site without having to sign in again on each page.
This website sets cookies that are technical and necessary for the function of the website, for example, that allow you to browse the website and use the different options included in this for the management of the website and enable its functions and services, such as controlling data traffic and communication, identifying the session, etc.
Some of the cookies we commonly use are listed below. This list is not exhaustive, but it is intended to illustrate the main reasons for which we typically set cookies. This website may set some or all of the following cookies:
| Cookie Name | Description | Cookie Category | Domain | Expiry |
|---|---|---|---|---|
| custom_timeout | This cookie is generated by the portal java system. This is used to hold the idle session time of user and logout the user forcefully post reaching the configured idle session timeout parameter. |
First Party - Strictly Necessary |
japp1.pshcm.tcsapps.com |
session |
| JSESSIONMARKID | This is generated by the Portal Java Server. This is a second session id which will be generated at login as well as mitigate further security risks. |
First Party - Strictly Necessary |
japp1.pshcm.tcsapps.com |
session |
| MYSAPSSO2 | The MYSAPSSO2 cookie is a non-persistent cookie that is stored in the browser's memory. Its value is the encoded content of the SAP Logon Ticket. After a user authenticates on a ticket issuing system, the system issues the user a logon ticket, which the user can use for access to successive systems. |
First Party - Strictly Necessary |
.pshcm.tcsapps.com |
session |
| saplb_* | The application cookie is used only by the SAP Web Dispatcher (or a third party load balancing solution) for instance-based load balancing. |
First Party - Strictly Necessary |
japp1.pshcm.tcsapps.com |
session |
| SAPWP_active | The SAPWP_active cookie informs the backend server (ITS, WAS, etc.) that the Web application has started in a portal environment. |
First Party - Strictly Necessary |
.pshcm.tcsapps.com |
session |
| JSESSIONID | The AS Java uses this type of cookie for session tracking. |
First Party - Strictly Necessary |
japp1.pshcm.tcsapps.com |
session |
| PortalAlias | The PortalAlias cookie is set on the first request to the Gateway Servlet to store the alias value of the Portal when calling other navigation related applications such as the Navigation servlet. |
First Party - Strictly Necessary |
japp1.pshcm.tcsapps.com |
session |
| sap-XSRF_EDP_<nnn>
nnn = Client ID |
This cookie is used for prevention from CSRF attack is based on keeping security token during user’s session and providing it with every modify operation (PUT, POST, DELETE). |
First Party - Strictly Necessary |
aapp1.pshcm.tcsapps.com |
session |
| sap-ext-sid-backup | It contains the mappings between ESID (External Session ID) and application server instance relevant for the current browser session. This cookie can be used to restore the ESID knowledge in the newly started SAP Web Dispatcher after a failover. |
First Party - Strictly Necessary |
aapp1.pshcm.tcsapps.com |
session |
| sap-usercontext | User context cookie is used when user starts a transaction (an ABAP program), it holds client alias and default language information.This will be passed to SAP GUI. |
First Party - Strictly Necessary |
aapp1.pshcm.tcsapps.com |
session |
| messagebarInfoVisible | Generated by ABAP system to indicate the status bar for web GUI applications. |
First Party - Strictly Necessary |
aapp1.pshcm.tcsapps.com |
session |
How to Control Cookies Manually
You can set your browser:
• To allow all cookies
• To allow only 'trusted' sites to send them
• To accept only those cookies from websites you are currently using.
We recommend not to block all cookies because this website uses them to work properly.
Please read below points to find out how to manage cookies in the major browsers.
Google Chrome:
Click on the “Menu” tab in the upper-right corner and then click on “Settings”.
To block cookies:
Settings → Click on “Advanced” to expand → Under Privacy and Security, Click on “Content Settings” → Click on “Cookies” → To block cookies, Click on toggle button next to this line “Allow sites to save and read cookie data (recommended)“ → This will block the cookies.
To check cookies:
Settings → Click on “Advanced” to expand → Under Privacy and Security → Click on “Content Settings” → Click on “Cookies” → See all cookies and site data → Click on the website and check the cookies used in that particular site.
Mozilla Firefox:
Click on the Menu tab in the upper-right corner → Click on Options → In the left side navigation, Click on Privacy and Security → Under History, Select “Use Custom setting for history” from the Drop down → Click on Show Cookies Buttons → Select the file which you want to remove and then click on remove selected button.
Internet Explorer:
Open Internet Explorer → Click on Tools menu in the upper-right corner → Click on Internet Options → This will open a window with many tab → Click on Privacy tab → Under Settings, move the slider to the top to block all cookies or to the bottom to allow all cookies → Then click Apply.
Open Internet Explorer → Click on Tools menu in the upper-right corner → Click on Internet Options → This will open a window with many tabs → Click on Privacy tab → Click on Sites button → Enter site name and then click Allow or Block button → If user clicks block button, that website is not allowed to use cookies in IE → Then click Apply.
Edge:
Click on the Menu tab in the upper-right corner → Click on Settings → In the left side navigation, Click on Cookies and site permissions → Click on Manage and delete cookies and site data → Under Allow sites to save and read cookie data (recommended), move the slider to the left to block all cookies or to the right to allow all cookies.
To block cookies for a website:
Click on the Menu tab in the upper-right corner → Click on Settings → In the left side navigation, Click on Cookies and site permissions → Click on Manage and delete cookies and site data → Under Block, click on Add button → Enter site name and then click on Add button. → If user clicks Add button, that website is not allowed to used cookies in Edge.
To allow cookies for a website:
Click on the Menu tab in the upper-right corner → Click on Settings → In the left side navigation, Click on Cookies and site permissions → Click on Manage and delete cookies and site data → Under Allow, click on Add button → Enter site name and then click on Add button. → If user clicks Add button, that website is allowed to used cookies in Edge.