Enhancements and Changes in Version 6.1
Changes introduced in version 6.1 of Cantara Integration Platform include:
- Cloud Security
- SFTP Authorization for Media Objects
- Tenant Scheduler Auto-Start
- OAuth2 Refresh Token Disabled for De-Authorized Users
- Cantara Legacy API default Response Format
- Minimum JDK Release Updated
- WebLogic Support Updated
- Cantara Scheduler Negative Day Offset for Period Date Trigger
- Trust Added to User Management Methods
A brief description of these changes is provided below.
Increasing the security of Cantara cloud deployments, Cantara software is now protected by Google Cloud Platform container analysis and vulnerability scanning. Automatic scanning of Cantara software deliverables adds another layer of assurance for business data. Full details about the capability are available from Container analysis and vulnerability scanning | Google Cloud.
SFTP Authorization for Media Objects
Cantara 6.1 adds secure communications for Media Objects, enabling SSH encrypted data connections for mobile devices in the field. Media objects allow Cantara users to attach marked-up photos, pdf files and other attachments to work orders. This extra detail can be very useful for storing inventory parts images and specifications relevant to a particular asset, which a parts interpreter will know but a service mechanic may not. Media objects can also be used to capture images of equipment wear or damage, or to draw attention to circled engine parts requiring repair. SFTP authorization ensures that Cantara media objects can be trusted with potentially sensitive data attachments.
Tenant Scheduler Auto-Start
The tenant scheduler now supports automatic start-up upon server restart. This improves Cantara's recovery from disruptions, particularly for on-premises environments. Services are restored without the need for manual intervention, minimizing downtime.
OAuth2 Refresh Token Disabled for De-Authorized Users
Disabling a user's single sign on account now triggers disabling of JDE access as well. This ensures that de-authorized users who are already logged in will not be able to continue accessing JDE services through the Cantara API. This is an important feature for reducing the risk of a data breach.
Cantara Legacy API default Response Format
To maintain full compatibility with Cantara 4 and 5 applications, the Cantara 6.1 API provides response data that is XML-formatted by default. Requests which specify a particular response format (either XML or JSON) will continue to be honored. Note that Rinami recommends that requests should always specify a required format, rather than relying on a default format.
Minimum JDK Release Updated
The minimum JDK version required by Cantara 6.1 servers has been upgraded to JDK 11, ensuring modern support and security for the platform. For customers whose deployments include a Cantara Agent server, note that the agent server will now only upgrade automatically if the required JDK version has been installed.
WebLogic Support Updated
Cantara now supports Oracle WebLogic version 14.1.1. Details of the enhancements provided by this release are available from Announcing Oracle WebLogic 1411.
Cantara Scheduler Negative Day Offset for Period Date Trigger
The Cantara scheduler now supports period date triggers defined as a negative offset in days. This enables customers to configure report scheduling configurations such as the day before a new period begins.
Trust Added to User Management Methods
Cantara 6.1 adds support for Trust authentication, and as of version 6.1.8, SAML. The full list of supported user management methods now includes JDE, Cantara, LDAP, OAuth2 (including Azure AD and Firebase), SAML, Everest SSO, Steltix TLX10, and Trust.