Allegheny County Move to Closed Security with ALLOut

Allegheny County successfully upgraded their JD Edwards EnterpriseOne 9.0 system by implementing the ALLOut Security tool-set. The upgrade involved restructuring their menu management, introducing process-based roles, and converting to a closed security model. These improvements streamlined their system, enhanced security, and facilitated a smooth merger with the City of Pittsburgh’s financial management systems.

Client in Focus

Through vigorous oversight of Allegheny County’s operations, services, spending, and contracts, the Office of the Controller utilizes every tool available to enhance the public’s trust, bringing county finances and spending into the public eye, conducting audits that meet the highest professional standards, and engaging in timely communications with county officials and the average taxpayer alike on the most relevant fiscal issues facing county government.

Client in Focus

Discover our industry leading expertise

Industry Insights

Spring Clean Your JDE Security and get back to peak fitness!
July 1, 2021
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!

Unravelling the Truth: De{Code} the Secret to Success with ALLOut
September 29, 2022
In this session, we unravel the truth behind the security features in standard E1 and how the ALLOut toolset complements these to optimize your daily processes.
Watch On-Demand

Upcoming live events

Escape Legacy JDE Security Tools: A Faster, Cheaper, Native Upgrade Path
January 13, 2026
Many customers of other JD Edwards Security solutions still struggle with heavy SoD, compliance, and security workloads driven by poor visibility, inefficient processes, rising costs and limited resources.
Register Now

Empower your security team

Save time, enhance risk visibility and be audit-ready with ALLOut Security for JD Edwards.

Request a Demo

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.

Allegheny County Move to Closed Security with ALLOut

Allegheny County Move to Closed Security with ALLOut

Client in Focus

Challenge

Solution

Results

Products Used

CombiRoles

ProfilePlus

SecurityPlus

Download the full case study and discover Allegheny County's move to closed security with ALLOut

Client in Focus

Discover our industry leading expertise

Industry Insights

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

On-demand webinars

Unravelling the Truth: De{Code} the Secret to Success with ALLOut

Upcoming live events

Escape Legacy JDE Security Tools: A Faster, Cheaper, Native Upgrade Path

Empower your security team