![Jd edwards solution explorer](https://kumkoniak.com/116.png)
They only have to periodically refresh the password of their network account. In fact, a JD Edwards User never needs to think about the JD Edwards password anymore. That way you are always sure that the passwords get refreshed in time without bothering the end users with this task. You can schedule this command to run every month via the regular Windows Scheduler application. When all Active Directory accounts that need to log in using Single Sign-On have been linked, you can run a command to have the JD Edwards password reset. Instead of manually linking the Active Directory account to the JD Edwards Users, you can also add all this information to an Excel sheet and upload it to the JDE SSO AD Admin Tool. This is all optional, because you can also add this information to the special JDE SSO login URL that users will use to access JD Edwards. You can also set up the environments to which the JD Edwards User can login and specify the Role that should be used. In this case the account of “k.oostdijck” is linked to JD Edwards User “QKOS”. When you double-click the listed user you will see the Window shown below, that allows you to link the Active Directory account to one or more JD Edwards Users. When an Active Directory account has been added to the JDE SSO Active Directory Group, it will show up in this User List after using the “Refresh User List” button positioned on the top left. In the example below, you see the way the GUI based JDE SSO AD Admin Tool works. When the installation of the JDE SSO executables on the Windows server has completed, you can use a GUI tool to maintain the setup. You will also add an extra Group in Active Directory that you can add to the network accounts that will be using the Single Sign-On to log in to JD Edwards. Part of the install is adding a few extra Active Directory attributes that JDE SSO uses to link the network account to the JD Edwards Users and to store the encrypted JD Edwards password. To be able to install JDE SSO you need to have a Windows Server (2003 or higher) that is set up to run the web server Microsoft Internet Information Server (IIS) and you need to have full access to the Active Directory that stores all the network logon accounts. Can be used in combination with regular logins (for a controlled and phased rollout).No need to manually maintain JD Edwards passwords.Supports multiple JDE accounts per user.JD Edwards Sign-On becomes smooth and prompt-less.Requires no changes to JDE configuration.Easy to setup, operational in just a day.
![jd edwards solution explorer jd edwards solution explorer](https://smartbridge.com/wp-content/uploads/sbblog_smartfieldsbody6-200x167.png)
Supports all JD Edwards releases from Xe (B73.3.3) upwards.Oracle® Validated Integration for JD Edwards® EnterpriseOne® 9.1 and 9.2 (also supports login to DAS ReportsNow®).Based on various customer implementations we deliver Everest SSO as our preferred Single Sign On solution for Oracle JD Edwards customers.
![Jd edwards solution explorer](https://kumkoniak.com/116.png)