JD Edwards
JD Edwards Single Sign On (SSO)
Having a single location for all credentials is critical for organisations who want to reduce the growing impact of Cloud Creep* as well as the frustration of forgotten usernames and passwords.
MyAccess benefits
Fusion5 developed MyAccess — a mechanism by which users can log into JD Edwards using Single Sign On (SSO). MyAccess is already being used by essential infrastructure organisations in both New Zealand and Australia.
Designed to use a range of OpenID Connect enabled identity providers (such as Microsoft Azure AD premium and Okta) as the source of authority, your Cloud Identity Provider can become the single source of truth for identification and authorisation for all applications within the organisation, whether those applications are cloud or on-premise.
MyAccess by Fusion5 offers your business SSO capability for JD Edwards at under half the cost of the current market alternatives. Pricing is available on application, simply fill out your details below and someone from our Innovation Team will be in touch.
Disarm new age security issues
Maintain user roles, decrease cloud creep, increase system security and tracking.
Increase productivity
Any existing integration with JDE that interrupts workflows can now be seamlessly accessed.
Ease of use
Less tabs, less waiting, better user experience.
Trusted local source
As your local JDE specialists, we can offer value and speed at reasonable pricinng.
Low disruption
You can use the standard programs for long username mapping, to ensure that there is nothing lost between the user’s old JD Edwards’ 10-character name and their cloud provider identity.
How does it work?
- JD Edwards User attempts login to JD Edwards
- MyAccess recognises the command and redirects the user to the Cloud Identity Provider
- Authentication and authorisation occurs with the Cloud Identity Provider
- MyAccess converts this authentication into JD Edwards authentication
- The JD Edwards user is then logged into JD Edwards
Are you ready for MyAccess?
For MyAccess to be implemented with maximum efficiency, the following must be in place:
- Azure AD or Okta is the identity provider which will be responsible for verifying the identity of users and applications that exist in an organisation’s directory, and ultimately issuing security tokens upon successful authentication of those users and applications
- An application that wants to outsource authentication to a Cloud Identity Provider must be registered in the Cloud Identity Provider, such as AWS — LDAP (on premise)
In a simple case, where a business is ready for MyAccess, Fusion5's components of implementation can be completed in 3-5 days.
NB: MyAccess is configured to use Azure AD and Okta as a standard offering. We can use other OAUTH or OpenID Connect compliant directories, however additional configuration would be required.
*Cloud Creep: When people within your business are adding cloud-based services or applications to the IT infrastructure, without ensuring due diligence around security and access paths.
