Multotec upgraded their JD Edwards EnterpriseOne 8.12 security system using ALLOut to streamline and enhance their security procedures. The project involved standardizing menus, implementing role-based access, and automating security settings, which significantly reduced implementation time. The successful transition resulted in minimal user issues, improved security maintenance, and effective SoD reporting.
Multotec manufactures and supplies a comprehensive range of products and services to the mining, minerals beneficiation, and power generation industries. Operating in seven countries with 19 locations, Multotec employs 1,500 people and generates an annual revenue of $150 million. Their expertise and extensive reach make them a significant player in these industrial sectors.
Multotec faced significant security management challenges during their upgrade to JD Edwards EnterpriseOne 8.12. The existing security procedures were outdated and inefficient, with redundant menus and tasks creating complexity and confusion. The key requirements for the new system included standardizing menus, reversing the open security architecture, implementing menu filtering, assigning multiple roles to users, simplifying security maintenance, and ensuring effective segregation of duties reporting.
Multotec selected the ALLOut Security for their security reimplementation. The project involved drafting a security framework that governed principles such as access by role and multiple roles per user. Using ALLOut’s SuperGrid module and SecurityPlus tool, Multotec established a new menu structure, defined roles with corresponding menu filtering, and automatically generated security settings for programs. This streamlined approach allowed for the rapid and efficient upload of multiple roles to over 400 users, significantly reducing the time required for implementation.
The implementation of the ALLOut led to a successful and smooth transition to the new security system. The project was completed efficiently, with the new security setup being tested and approved by end users before a seamless cut-over on a Monday morning. The effectiveness of the strategy was demonstrated by the minimal number of user support calls received post-implementation. This overhaul not only met Multotec’s key requirements but also simplified security maintenance, ensured proper role coverage, and provided robust segregation of duty reporting, ultimately enhancing the overall security framework of the organization.
We use cookies to give you the best online experience. By agreeing you accept the use of cookies in accordance with our cookie policy. You can always revoke your consent by clicking on the icon at the bottom left of the screen.
When you visit any web site, it may store or retrieve information on your browser, mostly in the form of cookies. Control your personal Cookie Services here.
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. |