Absent Member.
Absent Member.

Warning about box (box.com) connector

When installing the box.com connector, you MUST use an explicit proxy setting to obtain the OAuth token.

Yes, I know the documentation (and the Protect 2014 presentation) said you could use transparent proxy...

Yes, I know that if you try to use transparent proxy the first couple of screens will work correctly...

However, before you are done obtaining the OAuth token, when trying to use transparent proxy, you will have the machine's browser  get redirected to something like https://localhost:8443/oauth2callback?state=&code=eElEHo6lPnMgPk0JaiTz5jS44raMl where first the browser will complain about the certificate and then the connector will balk at the token being incorrect. The connector WILL fail.

But, if you specifically state the proxy settings (even for a transparent proxy), then the connector install WILL work.

So, until HP fixes the glitch, follow this advice and happily collect your box.com logs.

- Pete

Labels (2)
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.