Release 4.3
Support for user aliases (AAAS-13023)
In this release, a user can have one or more aliases in addition to the mandatory userID. Wherever a userID is specified in administration or authentication APIs, an alias can be specified instead. The userID and aliases are mutually unique. See the IntelliTrust Admin Online Help for more information.
Support for FIDO2 authentication (AAAS-12299)
This release supports FIDO2 tokens for authentication to SAML and OIDC applications as well as the IntelliTrust Administration and User portals. FIDO2 token authentication is available using the latest versions of Chrome, Microsoft Edge, and Firefox. See the IntelliTrust Admin Online Helpand User Help for more information.
Support for RADIUS IP attribute (AAAS-13024)
An optional field is available in the RADIUS application to select the RADIUS IP Attribute. The attribute specifies the IP address which can be used by IntelliTrust for RBA, including determining the user location. See the IntelliTrust Admin Online Help for more information.
Support for custom Mobile app activation schemes (AAAS-14126)
This release includes a new Scheme setting for smart credential and soft token apps to allow custom mobile applications instead of the Entrust Datacard mobile apps. See the IntelliTrust Admin Online Help for more information.
Gateway upgrade (AAAS-10547)
For post 4.3 releases, a Gateway upgrade button will be available to upgrade the gateway without having to reinstall, configure, and activate the gateway. Upgrades for earlier releases must continue to replace their existing gateway with the new one. It is strongly recommended that you upgrade to IntelliTrust Enterprise Service Gateway 4.3 to take advantage of this feature going forward.
Rename gateway and gateway instance (AAAS-12780)
This release supports renaming gateways and gateways instances.
Regenerate shared secret in Administration API applications (AAAS-12270)
This release supports regenerating an Administration API application shared secret.
Changes to IntelliTrust APIs (AAAS-13501, AAAS-13688, AAAS-13689)
- You can specify a user alias anywhere a userID is specified in the API. For example, this includes specifying a userID in any of the authentication API controllers.
- In the administration API, new attributes have been added to the User and UserParms structures to specify user alias values when fetching or modifying users.
- In the administration API, new controllers have been added to manage FIDO tokens for users. This includes the ability to get, delete, and update FIDO2 tokens.
- In the administration API, new controllers have been added to do paged searching of audits and assigned tokens with search criteria. Additionally, a new option to search for locked users has been added to the user search criteria.
All changes are backwards compatible. A customer application written to use the APIs provided with 4.2 will continue to work without change.