Getting the session cookie (Firefox)

The cookie varies from session to session and must be obtained from a browser while accessing the
page of interest:

1. Login as the affected user

2. First of all, navigate to the problem page in HCM
3. Open the Options Window > Privacy > Show Cookies... > Search for "ORA_FND_SESSION"
4. There will be one cookie matching this search pattern that has the DB SID as suffix. This is the
cookie of interest.
5. Select the part of the CONTENT of the Cookie between colons, as shown

6. In Chrome, click on the Spanner icon > Options > Under the Hood > Content Settings... > All
cookies and site data ...
7. You cannot search for ORA_FND_SESSION, you have to drill down via the site to find it, the site
will be the same domain name XXX.com as the Fusion Apps page URL.
8. In IE, I'm afraid it cannot be found at all. A session_id can be found from fnd_sessions by
searching for user_name and a last_connect around the time of the connection.
9. No need to remain logged in after collecting the cookie.
10. Please provide the results in spreadsheet format.

This will show all the security setup that this user is inheriting when logging in, and will also reveal the
WHERE clause restrictions that are applied from Security Profiles.

Two other ways to get the cookie (Firefox)

1. In Firefox, go to Tools>Page Info. Select Security section, Click View Cookies, search for "ORA_FND".
Select the row which contains the SID of your database.

Copy the Content between but not including the colons.

2. In Firefox
Log in as problem user
Navigate to one step before your problem page
Press F12 to toggle developer tools
Select Network tab
Now navigate the final step which gets you to the problem page
Click on the first GET line (usually with longest time shown)
Click on Cookies subtab
Search for ORA_FND_SESSION
Choose the matching row which contains the DB's SID
Click on the value, and copy that
give this value to Dev, and we will give you back the data security query to run.
Getting the Cookie (Chrome) - The following steps were carried out in Google Chrome version :
38.0.2125.77

1. Login (using the fusion application user credential who faces the issue) into the Oracle Fusion
Application and Navigate to the Page where you wish to extract the Session Cookie from. E.g:

2. In the top right corner of the Chrome browser, you will see a three horizon lines icon :

Click on this icon and you see a drop down list menu. Select the ‘Settings’ option.
3. This will launch a new Browser Tab and will display the Setting Screen.
4. Scroll to the bottom and expand the ‘Show Advanced Settings’ region.
5. Under the ‘Privacy’ sub-section, click on the ‘Content Settings..’ button

6. This will launch a pop-up window and in this window under the ‘Cookies’ section press the ‘All
cookies and site data..’ button

7. In the Cookies and site data pop-up window, click on the ‘Search Cookies’ text box on the top
right corner.

8. Type ‘oracle.com’ (without the single quotes) and you will see an entry appear in the search
results. For hosted Customer PODS in Oracle cloud, please type ‘oraclecloud.com’ instead.
9. Click/highlight the oracle.com or oraclecloud.com entry.

10. Click on the ORA_FND_SESSION_<Your Instance Name> cookie button. This will open up the
cookie content values:
 11. We are interested in the ‘Content’ value which is a very long alpha-numeric string value. You can
highlight and select it into the clipboard.

12. Paste the value into a text editor and select the alpha-numeric string value that appears between
the two colons ‘:’ without the colons themselves

I have highlighted in red bold in the below example.

DEFAULT_PILLAR:/PZwPXUIjpy7/6Pjxg4My3Q10Rg1Z+Hw1P6eSpqsh6dUjKGfHsuAw87UBGLw/t//:
1412000499201

An alternative method to get the cookie (For SaaS customers – this may need to be performed by
Oracle Support)

Users who have only IE access cannot get the cookie. Or if there has been no success with the above
methods, then try to get the output of

nullSELECT session_cookie FROM fnd_sessions WHERE user_name='<put user name here>' AND
product='PER'; }}}

substituting the user's actual username. There may be several results, choose one. The records from
fnd_sessions do expire after a period of time, so using a cookie that is more than a day or two old is not
recommended.