By Paul In 't Hout-Oracle on Sep 28, 2015
User-ID's are valuable information
- Who are my most active users?
- Who generates the most errors on my website?
- Which clients had to wait the longest to use my online service?
- How can I quickly find the data of the user who's complaining to me on the phone about the service?
Session Tracking Should be Functioning Properly
How RUEI Finds the User ID
- URL Argument: These are values on the GET string, or in the POST arguments. Like "Paul" in login.oracle.com?user=Paul
- Cookie: A cookie with a static value containing the user-id. Note this is not the same as a session tracking cookie.
- Custom Pattern: Define a "before" and "after" text match value that always occurs before and after the user-id in the html source.
Two Examples of Finding a User ID
- In both Chrome or Firefox hit F12 to pull up the developer view. Then navigate to the 'Network' tab for insight into cookies being send and received. In this document we will use Chrome.
- Ensure that 'Preserve logs' is ticked.
- When you click the 'login' button, you are re-directed to login.oracle.com where the user-id and password need to be provided:
- Since the login details have not yet been provided. It's a good time to clear the data gathered in the network tab thusfar. This will make sure that the next action will be at the top of the list.
A good thing as the next action is likely going to be where the user-id is provided.
- Now, do the login.
- The very first hit done by the browser is a POST to auth_cred_submit. When we open the details we can see with POST Argument contains the user-id information.
Don't worry about the password being visible in plain text. At this stage it's not been encrypted yet, but it has been before it was send to the server.
- The configuration we need to enter in the RUEI application configurations is:
Source Type: URL Argument
Source Value: ssousername
- Look to see if the web-application shows the user-name anywhere visible on the screen right on the landing page.
- When found, righ-click on the page and select 'View Source'. This will bring up the HTML source.
- Search for the user-id in the source.
- Find a suitable 'before' (in green) and 'after' (in red) pattern. Make sure that this text does not contain any variables that may change from user-to-user.
- The configuration we need to enter in the RUEI application configuration is:
Source Type: Custom Pattern
String Start: <li class="dropdown"><a href="#" class="dropdown-toggle" data-toggle="dropdown">
String End: <b class="caret"></b></a><ul class="dropdown-menu">
Reference Documentation and Knowledge Base Articles
- RUEI 188.8.131.52 User Guide 8.3.14 Defining User Identification
- How to include a session tracking cookie for RUEI in EBS using professionalization. (Doc ID 1643747.1)
- This document is also available on My Oracle Support under Doc ID 2060067.1