JD Edwards AIS Single Sign On

Proxy end-users via AIS to honor native JDE security and data access, eliminating the need to code/redefine security on the code.

Why?

You want to utilize AIS under the context of a specific end-user without having the end-user password. You need this because you want all the end-user permissions and settings to be honored.

This scenario typically occurs when developing portal/web-based integrations where you only want to retreieve the data and perform actions that the end-user actually has access to. If you don't use this approach, and decide to use an application account, you will most likely need to perform security checks and data filtering on your custom code.

Software Requirements & Dependencies

• Tools Release 9.1.4 or higher
• JAR files needed on classpath
• AIS_Client (obtain from JDE Update Center/Change Assistant)
• Jackson Annotation, Core, and DataBind (these are distributed with AIS_Client)
• JavaTokenGenerator from a E1 Web Client (obtain from webclient.ear\webclient.war\WEB-INF\lib)
• Base_JAR from a E1 Web Client (obtain from webclient.ear\webclient.war\WEB-INF\lib)
• TokenGen.ini (sample on root of the repo but modify to match you SSO setup)

JD Edwards SSO Configuration Requirement

You will need to add a new node, define the token lifetime, and set it up as a trusted node to your existing enterprise server (security server). All high-level steps are shown on the [Security Administration Guide] (https://docs.oracle.com/cd/E24705_01/doc.91/e24258/setup_jde_e1_sso.htm#EOTSC00406) but are detailed below. The SSO Environment Configuration Tools application is where all the actions need to be performed and it can be accessed via Security Maintenance Advanced and Technical Operations under GH9052.

1. Verify your existing Enterprise server is already defined as a SSO node. If not, you will need to add it and define its token lifetime.

2. Add a new Node for AIS. In our case we are using the generic name SSO4AIS, as show below. The password will need to match the password used inside the TokenGen.ini (which must be on classpath of your application. There is a sample of a TokenGen.ini on the root of the repo)

3. Setup the Token Lifetime for the new node as show below. Change values as needed/desired.

4. Setup the new node as a Trusted Node to your enterprise server

5. Restart enterprise server