Supporting Multiple Roles in JD Edwards Xe to 9.2

Whitepaper Abstract

Part 1: Benefits of Role Based Security
We explain the benefits of using role based security and why it is such a significant improvement on a “one role or group per user”.

Part 2: Security Limitations in Xe – 9.2
We discuss the limitations of security in Xe – 9.2 in relation to the support of multiple roles (or Groups). This section explains how ALLOut SuperGrids and ALLOut CombiRoles overcome these limitations.

Whitepaper Abstract

Part 1: Benefits of Role Based Security
We explain the benefits of using role based security and why it is such a significant improvement on a “one role or group per user”.

Discover our industry leading expertise

Industry Insights

Access Management in JD Edwards (JDE) Security
July 1, 2021
Access management is the process of identifying, tracking, controlling and managing authorized or specified user's access to a system, application or any IT instance.

Working with Security Roles in JD Edwards
February 4, 2020
The ability to use security roles as a building block of your security efforts is an incredibly useful tool. How do you make the most of it in your implementation or daily processes?
Watch On-Demand

Upcoming live events

BLUEPRINT 4D – Las Vegas!
9 Jun 2025, 12:00 am
Join the ALLOut Security team at the Venetian in Las Vegas, for what’s set to be yet another engaging conference!
View Event
Implementing Access Change Control in JD Edwards
May 21, 2025
In this joint webinar hosted by ERP Suites and supported by ALLOut Security, you’ll learn how to implement a secure, repeatable process that protects production environments without slowing down your team.
Register Now
SoD Risk in JDE: See it. Control it. Prove it.
July 16, 2025
Our next-generation SoD solutions are designed to meet the needs of modern GRC initiatives, tailored to IT, Finance, Audit, and Security teams alike. Align SoD oversight with your evolving control environment through consolidated processes that scale across hybrid environments, cloud platforms, M&A activity, and cross-application integrations
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.

Supporting Multiple Roles in JD Edwards Xe to 9.2

Supporting Multiple Roles in JD Edwards Xe to 9.2

Whitepaper Abstract

Downloads

Whitepaper Abstract

Discover our industry leading expertise

Industry Insights

Access Management in JD Edwards (JDE) Security

On-demand webinars

Working with Security Roles in JD Edwards

Upcoming live events

BLUEPRINT 4D – Las Vegas!

Implementing Access Change Control in JD Edwards

SoD Risk in JDE: See it. Control it. Prove it.

Empower your security team