REST shim / tracing capability - verbosity

Idea ID 2785462

REST shim / tracing capability - verbosity

The tracing capability of the REST shim is quite low. When troubleshooting the authentication you have to use a proxy application to allow "man-in-the-middle" troubleshooting. It will help far more when you could see what the shim is actually sending when doing its GET/POST/etc.
It should also allow more of debug level trace for OAuth flows, at least when it comes to complex OAuth flows.
When using mutual authentication it should also be able to trace the use of the client certificate of the configurable keystore.

-> The REST shim trace should be more verbose.
5 Comments
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Accepted

This request is under development and would be available with the next release of REST driver.

Knowledge Partner
Knowledge Partner

and could we make sure that the Azure driver which uses the REST shim also picks up this functionality?

Super Contributor.
Super Contributor.

The alternative is to call everything using a proxy for REST connector for outgoing communication with external service, in proxy where you can trace what's going out and coming in.

 

/maqsood.

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
The next minor release for Azure driver would have better-tracing capability.


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.