Oracle EBS Connector
We have made a change to our Oracle EBS connector so that when the password is updated, Oracle EBS system's password_date field will get updated with the new timestamp, in addition to the last_update field.
Oracle EBS connector only supported SID to connect, this has been extended to use either ServiceName or SID.
When there is only a single node in the Chain of Trust, we will now start the remediation process for users as they get certified, as opposed to waiting for all users to be certified.
Windows Authentication for SQL Server Connector
SQL server connector now supports windows authentication. Please check the ‘Use Windows Authentication’ check box in the connected system detail page to turn on windows authentication for the system.
To use windows authentication, mssql-jdbc_auth-<version>.x64.dll or mssql-jdbc_auth-<version>.x86.dll (depending on 64 bit or 32 bit java) needs to be in the java.library.path. The installer will copy the appropriate .dll file, based on the java version, to the agentdll folder (under IDENTITY_HOME, DATAFORUM_HOME or GIG_HOME based on the installation).
The current sql server jdbc driver version is 8.4.1. Therefore, the name of the .dll file will be either mssql-jdbc_auth-8.4.1.x64.dll or mssql-jdbc_auth-8.4.1.x86.dll.
We can either copy this .dll file to one of the current java.library.path or update the java.library.path to point to the agentll location in tomcat.
Example setting in catalina.bat:
set CATALINA_OPTS=%CATALINA_OPTS% -Djava.library.path="%PATH%";"C:\Fischer\IdM\identity\agentdll"
JDBC driver’s .jar location when using multiple contexts in the same tomcat
The mssql-jdbc_auth-xxx.dll file is loaded by the mssql jdbc driver to perform windows authentication. By default, the .jar file for the mssql jdbc driver (mssql-jdbc-8.4.1.jre8.jar based on the 8.4.1 version) will be available in the context’s WEB-INF\libs folder. However, if there are multiple contexts (such as identity and dataforum in the same tomcat), only one of the context will be able to load this .dll. In such scenarios (having identity and dataforum in the same tomcat or for gigs), this mssql jdbc driver .jar file should be manually moved to the tomcat’s libs folder, so that it will be shared by all contexts and the .dll file is required to be loaded only once.
List of defects reported by customers or implementation, does not contain defects raised internally.
- Fixed issue leading user to re-login after taking action on a compliance exception.
- Fixed manager value not being shown in the beneficiary details screen of the certification items.
- Fixed issue with workflows being hung as a result of blocking GIG calls.
- Fixed issue causing policy memberships not being revoked correctly.
- Fixed issue with Remove Field mapper rule configured by selecting the attribute itself.
- Fixed issue with security question answers being individually flagged as correct or incorrect.
Please sign in to leave a comment.