Created by Daniel Kutac, Sales Engineer, InterSystems
At this time, there is no formal documentation available for this functionality in any of released or pre-release (field test) products.
For experimenting with Caché OAUTH implementation, Caché 2016.2 or higher is needed. At the time of writing this document, Caché 2016.2 and 2016.3 are available as field test downloads for registered partners.
Note that at this time, OAUTH is still under development and is an unsupported feature. If you need any information about OAUTH in Caché 2016.2 or 2016.3 that goes beyond the scope of this article, please contact your InterSystems technical representative.
Part 3. Appendix
Caché OAUTH classes explained
In the previous part of our series we have learned about configuring Caché to act as an OAUTH client as well as authorization and authentication server (by means of OpenID Connect). In this final part of our series we are going to describe classes implementing Caché OAuth 2.0 framework. We will also discuss use cases for selected methods of API classes.
The API classes implementing OAuth 2.0 can be separated into three different groups according to their purpose. All classes are implemented in %SYS namespace. Some of them are public (via % package), some not and should not be called by developers directly.