I am happy to share with you that OTK and MAG 4.0 have been released. Both come with smaller and bigger changes. The main enhancements were made on this topic:
- Enable the easy button upgrade
OTK and MAG now have specific policies that are marked as customizable where others are either implemented or suggested to be read only. This enables us to provide a smooth upgrade procedure. Whatever has been implemented in the customizable policies will NOT be replaced with an upgrade.
In the area of customizations we are distinguishing between two different types:
- configurations: configure attributes such as token lifetimes in dedicated policies
- extensions: extend features OTK provides such as adding your own grant_type in dedicated policies
Both types are implemented as policy fragments that are included in read only policies. The ones made for configurations are generally named like the target policy but with a '#' sign as prefix (e.g.: OTK Token Lifetime Configuration becomes #OTK Token Lifetime Configuration). In this case you would copy a variable from OTK Token Lifetime Configuration and paste it into #OTK Token Lifetime Configuration and set it to your desired value.
The policies for extending OTK's features are generally named with a suffix such as ' ... Extension' (e.g.: OTK User Authentication becomes OTK User Authentication Extension).
Here is a list of my personal highlights of the new release:
- Upgrades as of 4.x are easy
- OTK now supports a configurable number of sessions per resource_owner/ client which was limited to 1 in the past
- OTK now supports JWT signatures with RS256 out of the box
- OTK now maintains the database (MySQL and Oracle) through a scheduled task. There is no need anymore for an external cron-job
- Extensions can be used to support custom id_token creation and validation
- Extensions can be used to support custom grant types
- OTK uses only two single locations where local cache assertions are used. With that its very easy to replace the local cache assertion with a remote cache assertion and its also easy to audit all data that is being cached and retrieved
- The Authorization Server's login and consent pages can be modified easily
- Many configurations/ extensions can be configured per client by leveraging the custom field per client and client_id in OAuth Manager. This should introduce a huge fexibility
MAG received updates but here is my favourite one:
- A new feature is the so called enrollment process. This enables an enterprise to publish an app in the app store with a minimal configuration. The full configuration can be retrieved at runtime which makes it very flexible
I surely missed some other enhancements but I wanted to highlight the ones above. If you have further questions or if you need guidance on how to use OTK and MAG as of now please leave a comment. For the complete documentation please go here and search for CA API Management OAuth Toolkit or CA Mobile API Gateway: Documentation