REST shim / support more/contemporary OAuth flows

Idea ID 2785447

REST shim / support more/contemporary OAuth flows

When authentication requirements are high/more complex for security reasons, customers might require grant_types "Authorization Code" and "Refresh Token" - in a setup that includes Access Manager, for instance. The REST shim as documented supports grant_types "password" and "client_credentials".

-> The shim should support more/contemporary OAuth flows.
4 Comments
Absent Member.
Absent Member.
Like OAuth2.0 Three-Legged Authentication
Respected Contributor.
Respected Contributor.
Am also trying for BOX Application integration. PLease help us for 3 leg authetication in further revisions.
Super Contributor.
Super Contributor.
Authorization Code flows is not interactive applications, not for Identity integration scenarios for the NetIQ Rest shim.
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Delivered

Enhancement was delivered as part of the REST driver 1.1 release.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.