InterSystems IRIS 2025.2.0 introduces several features to improve the user experience of configuring OAuth2.
- OAuth2 is now a native authentication type and can be easily enabled for your services and web applications. Previously, OAuth2 was a type of delegated authentication.
- You can now create resource servers with the new OAuth2.ResourceServer class, which simplifies resource server configuration significantly. Previously, resource servers were instances of OAuth2.Client.
- The OAuth2.
The InterSystems PKI is for testing purposes only. Do not use it in a production setting.
As of today March 26, 2024, the InterSystems PKI is now deprecated.
For Microsoft Windows, please consult the InterSystems product documentation.
The IRIS installer will detect if a web server is installed on the same machine, which gives you the option to automatically have the web server configured.
All Apache installations will require sudo (recommended) or root permission to install the web server. This requirement supports recommended best practices.
If you would like to try the new installation process for the NoPWS project, you can get access to the Early Access Program (EAP) here. (https://evaluation.intersystems.com/Eval/)
Once you have registered, please send InterSystems the email address you used to register for the EAP to nopws@intersystems.com.
Look here for background: Original Post
As previously announced at Global Summit 2022, InterSystems will discontinue shipping or installing an Apache-based web server (often referred to as the private web server or PWS); this change is currently planned for InterSystems IRIS 2023.2.
With this new approach, you have full control to choose which web server best suits your purposes, and how you configure, maintain, and update it. A key benefit of this change is that you will no longer have to wait for an updated kit from InterSystems to get the latest version, which is important especially in security vulnerability situations.
Beginning with InterSystems IRIS 2020.1, the minimum required version for AIX is AIX 7.1 TL4.
The InterSystems IRIS installer will detect if the required IBM XL C filesets are installed before continuing
with the installation.
With the recent release of macOS 10.15, Apple has tightened its control mechanism , called Gatekeeper, so that it now requires executables to be notarized. InterSystems products are not currently supported for use on macOS 10.15 and the executables have not been notarized. (As a reminder, InterSystems products are supported on macOS as a development platform only.)
InterSystems is pleased to announce a new Developer Download site providing full kit versions of InterSystems IRIS Community Edition and InterSystems IRIS for Health Community Edition. These are available free of charge for application development use.
You can download directly from the InterSystems Developer Community by selecting Download InterSystems IRIS.
Preview releases are now available for the 2019.3 version of InterSystems IRIS and IRIS for Health!
Container images are available via the WRC's preview download site.
The version number for these releases is 2019.3.0.302.0
Public announcements will be made shortly, with separate announcements for each product.
InterSystems IRIS Data Platform 2019.3 is a CD (continuous delivery) release of InterSystems IRIS. It has many new capabilities including:
Continuous Delivery Releases of InterSystems IRIS
Node-level Architecture for Sharding and SQL Support
Infrastructure and Cloud Deployment Improvements
Port Authority for Monitoring Port Usage in Interoperability Productions
X12 Element Validation in Interoperability Productions
Conversion Sequence step 4 (see table below)
Over the last few months, we have made changes to InterSystems IRIS to make it easier for you to move from Caché/Ensemble (C/E) to InterSystems IRIS. The most significant adjustments are the re-introduction of non-Unicode databases and the in-place conversion. InterSystems IRIS now fully supports non-Unicode databases with all the functionally that already exists with Caché. The in-place conversion supports an upgradelike process to install InterSystems IRIS right on top of your existing C/E deployments.
The 2019.2 version of InterSystems IRIS Studio is now Generally Available!
InterSystems IRIS Studio 2019.2 is the first release of our cross-product Studio development tool. It can connect to InterSystems IRIS servers and also to Caché/Ensemble servers, and behaves appropriately for each. This helps developers that want to work across both sets of products as well as those that want do develop against containerized IRIS using Studio.
IRIS Studio is a separate download that runs on Microsoft Windows (Windows Server 2012, Windows Server 2016, Windows Server 2019, and Windows 10 for x86-64).
Caché 2018.1.2 and Ensemble 2018.1.2 maintenance releases are now available.
Full product installation kits can be downloaded from the WRC Software Distribution site.
For information about the corrections in this release, refer to the release notes.
This release adds support for Ubuntu 18.04 and Windows Server 2019.1 operating systems. You can see the details of all supported platforms inthis Supported Platforms document.
The build corresponding to this release is 2018.1.2.309.0
InterSystems is currently verifying InterSystems IRIS 2019.1 with Windows Server 2019. This work is scheduled to complete by the end of January 2019. In the second half of this month InterSystems will add Caché/Ensemble 2018.1.2 to be verified on this platform.
As we get closer to the completion of those tasks, I will update this post with information on release dates, and which products and version will support Windows Server 2019.
InterSystems has completed the verification process for OpenJDK 8.
Customers now have the option to either use the Oracle JDK, or the OpenJDK with all InterSystems products and versions that support Java 8.
Support for future versions will continue to be supported on both of these Java Development Kits.
Unconferences have been described as “networking on steroids.” They are the ultimate peer-to-peer discussion experience, and have been a vital part of InterSystems Global Summit for the past few years.
To ensure that this year's Unconference at Global Summit is better than ever, we want to know what YOU want to discuss with peers and industry leaders. Please follow the link below to submit your Unconference topic for 2018! Feel free to submit as many as you would like. Keep in mind that topics should be technology-related and relevant to conversations your peers will also be interested in.
InterSystems products (InterSystems IRIS, Caché and Ensemble) support AIX on Power 9 chips starting with:
Caché/Ensemble 2017.1.3
InterSystems IRIS 2018.1.1
Effective immediately InterSystems will no longer support Health Connect on Solaris. Previously released products starting with 2017.1 will also no longer offer this combination. This is in line with InterSystems HealthShare, which is not available on this platform.
As previously announced, 2017.1 on VSI OpenVMS 8.4-1H1 is the final major version of Caché and Ensemble. 2017.1 will not be available for VSI OpenVMS versions beyond 8.4-1H1.
Maintenance releases of 2017.1 on VSI OpenVMS may be announced but only to deliver critical corrections. 2017.1 on VSI OpenVMS will be the Minimum Supported Version from July 1, 2019 through December 31, 2020. After December 31, 2020, no further maintenance releases will be made available.
InterSystems has performed various system and application benchmarks to determine the potential performance impact after the corrections for Meltdown have been applied.
Overall our tests have shown at worst a performance degradation of less than 2% and in some cases slightly better performance, but within the margin of error of testing. All tests confirm that the specific performance impact to a deployed application is directly related to how this application is using system resources. Specifically, this means that in certain cases (e.g. a query) a larger performance impact is possible.
Project related quality assurance efforts have revealed a number of concerns for the current release of 2017.1.0 and 2017.1.1 on all OpenVMS platforms. In certain situations, the impact can be severe. InterSystems will address these issues with the upcoming 2017.1.2 release, and in the meantime, will remove all 2017.1.x kits for OpenVMS from our Download Servers.If you have immediate needs correcting existing deployments of this version, please contact the InterSystems WRC (support@intersystems.com).
With the recent release of Caché and Ensemble 2017.1, InterSystems customers can now create configurations where the data-at-rest cryptographic library used is compliant with FIPS 140-2.
Caché and Ensemble now provides you with the option to enable FIPS mode on RedHat 6.6, 7.1 on x86-64. This means is, that InterSystems products will no longer use the supplied crypto libraries that come with the kit, but will use the FIPS validated libraries provided by the Operating Systems vendor.
To configure your system, RedHat must operating in FIPS mode.
The last version of Caché, Ensemble released for VSI OpenVMS is 2017.1. Unlike HP OpenVMS (Alpha and Itanium), VSI OpenVMS on Itanium continues to be supported. This means that critical corrections or changes required to support customer’s hardware purchases will all be based on 2017.1 or earlier versions.
Related announcement: https://community.intersystems.com/post/platform-compatibility-hp-open-…
Beginning with the next release after 2017.1, InterSystems products will no longer be offered on macOS (OS X) as a Server platform. This platform has been re-classified and will be available as a Development platform in future releases.
Starting with 2017.1, InterSystems is adding Ubuntu (64-bit) as a third linux server platform. Prior to 2017.1 Ubuntu was already available as a development platform and customers could use InterSystems distributions build for SUSE to run on Ubuntu. As a result there are a few license key implications for 64-bit linux versions starting with Caché and Ensemble 2017.
Starting with the Field Test of 2017.1 InterSystems products will include Feature Tracker. It is enabled by default during the Field Test and is explained more fully in the product documentation included below. Information collected by Feature Tracker is limited to technology usage information and instance identification. This tool has been carefully crafted to not transmit sensitive information related to customer applications or data.
Starting with 2017.1, InterSystems has moved macOS from being a server platform to a development platform. 2017.1 will only support macOS 10.12 and will no longer be available as dmg kits.
Verification of macOS 10.12 has not been completed at this time and Field Test kits for this platform are not yet available.
Presenter: Andreas Dieckow
Task: Apply SQL security to multiple servers in a distributed system
Approach: Provide code samples for using new API calls to apply SQL security statements to multiple instances of our products
Description: The requirement that started at all. See examples on how to use this new feature and integrate it into your application by discuss code examples.
Problem: SQL Security is local to the instance and most of time driven by customer application code. That it is only local to the instance and is not automatically going to other instances requires a solution.
Solution: With application code use new API calls to issue SQL security statements that is applied to multiple instances.
Content related to this session, including slides, video and additional learning content can be found here.
Presenter: Andreas Dieckow
Task: Securely store sensitive information
Approach: Give examples of data-at-rest encryption and data element encryption
Description: In this session, InterSystems will showcase how to use API calls to programmatically do everything using your own scripts. This approach is highly effective if you have recipe based settings and configurations that you would like to roll out in a controlled and fast fashion.
Problem: Implement Security relevant information correctly and how. Examples are Credit Card information, Sensitive information (e.g. SSN, Classified Information)
Solution: Data-at-rest encryption and data element encryption
Content related to this session, including slides, video and additional learning content can be found here.