All
Accepted answers
Andreas Dieckow · Mar 10, 2016 go to post

The title of the post is not quite correct. You would like to resolve something in the authentication step, not the authorization step. Please take a look at the ZAUTHENTICATE.mac in the SAMPLES namepace that includes a large array of options and code examples (most can be used just by uncommenting them). It also includes an example of performing 2 factor authentication. For this to work you have to validate the user's credientials first and then step into the 2 factor part of the authentication. Let me know if this helps. If not I will get you a more concrete implementaiton of ZAUTHENTICATE.

(Also please make sure that your authentication options for the service has the right list of options (in your case problably only delegate authentication)) 

Andreas Dieckow · Mar 23, 2016 go to post

InterSystems is going to use 1.0.2g (the now current version of OpenSSL starting with 2016.3. As we get close to the Field Test of 2016.3 the exact version might get updated. 1.0.2g will will introduce some backward incompatibilities related to SSLv2 and SSLv3. Once we have accessed how are we going to address those, I will post this information here and on the Compatibility Blog.

Andreas Dieckow · Feb 12, 2018 go to post

This is not an Atelier issue, but an issue of general concern. A system administrator might specify authentication but also allows for unauthenticated access. The instance will try to authenticate and if this fails will determine if there is another authentication option.

The authentication mechanism of unauthenticated was helpful at the time when it was created, but not anymore. It is too easy to leave a server wide open; something nobody can afford anymore. The minimal installation option will go away, and with it the default of having unauthenticated being enabled. Atelier is already based on the concept that all access to a server requires authentication.

Stay tuned for more changes in the area of product installation and install modes.

Andreas Dieckow · Feb 12, 2018 go to post

Hi Dmitry, the Atelier team has started to switch the Atelier release cycle to quarterly releases. Yearly released like we all observed between 1.0 and 1.1 are not helpful. Like so often when change is required there are wrinkles in time that will influence how quick this change will occur. We are experience this in the moment, but working diligently toward quarterly releases. InterSystems well established process is to report issues or enhancement request via the WRC. This will have to continue. The Atelier team is very careful and keenly aware that the prioritization of what gets done is important not only to InterSystems, but also to the users of Atelier. There are many strategic areas in which we need to succeed. I like the idea of public voting if appropriate and within a certain scope. We will introduce this in the future.

Andreas Dieckow · Jul 11, 2018 go to post

After the release of Atelier 1.3, scheduled for late August, Atelier will only receive critical software corrections, no enhancements.

Andreas Dieckow · Jul 16, 2018 go to post

Thanks for all your questions and comments.    A bit more of an explanation:

 

    We’re reviewing our plans beyond Atelier 1.3 in order to radically improve the developer experience with InterSystems IRIS Data Platform. 

    We welcome your ideas and feedback, and invite private communication to ensure that our plans are sound.  

 

    In the meantime:

·        If you are using Studio and happy with it, keep using it.   We are maintaining it indefinitely and are happy that there are so many active developers and that the community has expert advice as well as add-on tools that work with Studio.

·        If you are using Atelier and happy with it, keep using it, and look forward to version 1.3.   We are also maintaining it indefinitely.  We've reached a milestone and have many users that are productive and effective with Atelier, including combining it with other Eclipse plug-ins.   

·        If you are starting work with a new development group, use Atelier.   Eclipse is familiar to millions of developers, and Atelier is more than sufficient to get the job done.  Consult with us on these projects as you get going, because there are some areas such as Ensemble productions where developers may want to use Studio or other tools along with Atelier.

Andreas Dieckow · Feb 5, 2019 go to post

We currently anticipate that this version will be supported on Windows Server 2019, but we will have to wait for the conclusion of our verification process to be sure.

Andreas Dieckow · Feb 26, 2019 go to post

InterSystems has completed the verification process for running our products on Windows Server 2019.

  • InterSystems IRIS is now supported with 2019.1 and later
  • Caché and Ensemble are now supported with version 2017.2 and later

InterSystems found no issues and existing kits are supported.

Andreas Dieckow · Mar 15, 2019 go to post

I updated the original statement to include that with Caché and Ensemble 2018.1.2 we added support for two new platforms:

Ubuntu 18.04

Windows Server 2019.1

Andreas Dieckow · Jul 1, 2019 go to post

I think the link is not wrong, but stops at the directory above the components folder. Your link if our course on click faster ;)

Andreas Dieckow · Jul 18, 2019 go to post

No, the focus of this conversion is to enable existing C/E customers to move to InterSystems IRIS.

Andreas Dieckow · Oct 15, 2019 go to post

We will post container kits here as well. Those are released versions and not previews, that can be used for Development, but not for deployments.

Andreas Dieckow · Oct 30, 2019 go to post

Community kits (preview) for InterSystems IRIS and InterSystems IRIS for Health are now available from the Docker hub.

docker pull store/intersystems/iris-community:2019.4.0.379.0

docker pull store/intersystems/irishealth-community:2019.4.0.379.0
Andreas Dieckow · Nov 1, 2019 go to post

I am confused. The link above is for the IRIS for Health Community Edition. I would expect you get the IRIS for Health image. Please elaborate

Andreas Dieckow · Feb 2, 2017 go to post

The installation does in general not offer the option to place the core files of the system in different locations. Some aspects like new databases and journal file location can be changed later, as part of the system configuration. You seem to have already found the correct documentation for this.

Andreas Dieckow · Oct 5, 2017 go to post

On your second question: The grayed out option (Server's copy) and the missing equivalent options have not yet been implemented. All four ways should be available by the time 1.1 will be released.

Andreas Dieckow · Jan 2, 2018 go to post

Hi Jorge,

Field Test keys are provided for ongoing field tests. They are not extended after the Field Test version has been released, and are only provided for this program.

Respectfully,

Andreas