Spring Clean Your JDE Security and get back to peak fitness!

Over time there are frequently Users or Roles in your system that are no longer used, but they still have records associated with them. Time for a clean up and maintenance schedule!

Home » Industry Insights » Spring Clean Your JDE Security and get back to peak fitness!

Over time there are frequently Users or Roles in your system that are no longer used, but they still have records associated with them.

Regular maintenance of your User and security tables will help keep your system streamlined and running at peak efficiency. In addition, keeping your User count low may have licensing impact with Oracle.

Selecting the Delete Options form exit from PDIS0953 (User and Role Maintenance Screen) brings you to an interactive screen where you are able to define all of the records associated with a profile for purging. This is a great way to quickly purge the security records for selected or all Users, Roles, or *Groups that you have already identified as not being used without indadvertently leaving records in some tables or having to manage each set of information separately

Over time ‘duplicate’ security records may be created in the security table. These ‘duplicate’ records can be considered redundant or unnecessary due to the nature of the E1 security hierarchy. For exampleaccess to a Program or Version of a Program (including Data Selections and Processing Options) can be granted at the User, Role and/or *Public level.

A interactive application (PDIS0150) is provided which will identify these security records. Once highlighted this Program can also remove these records from the F00950. To access this functionality, select the Run UBE to delete duplicate Security from the ‘Security’ tab of the ‘Projects’ screen in the ALLOut toolset. We highly recommend you run this in proof mode first.

Your Spring clean should also look to delete Form Security Replicated at the Program Level, Version Security Replicated at the Program Level and Deleting User Security Replicated at the Role or Xe *Group Level.

These are a few steps in your regular security “Spring Cleaning” that we can help with. If you would like to learn more about these and other options, email hazel.jackson@alloutsecurity.com

Cookie name	Default expiration time	Description
_ga	2 years	Used to distinguish users.
_gid	24 hours	Used to distinguish users.
_ga_<container-id>	2 years	Used to persist session state.
_gac_gb_<container-id>	90 days	Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

visitor_id<accountid>	The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code.
pi_opt_in<accountid>	If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a `true` or `false` value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to `true`, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to `false`. The visitor cookie is disabled, and the visitor is not tracked.
visitor_id<accountid>-hash	The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information.
lpv<accountid>	This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.
pardot	A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking.

Cookie name	Default expiration time	Description
_ga	2 years	Used to distinguish users.
_gid	24 hours	Used to distinguish users.
_ga_<container-id>	2 years	Used to persist session state.
_gac_gb_<container-id>	90 days	Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

visitor_id<accountid>	The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code.
pi_opt_in<accountid>	If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a `true` or `false` value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to `true`, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to `false`. The visitor cookie is disabled, and the visitor is not tracked.
visitor_id<accountid>-hash	The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information.
lpv<accountid>	This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.
pardot	A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking.