Charles Hammitt

Cannot use S3/H3 api to communicate with HCP on machine outside of subnet / domain. REST works.

Discussion created by Charles Hammitt on Sep 24, 2015

Cannot use S3/H3 api to communicate with HCP on machine outside of subnet / domain. REST works remotely or on the same domain / subnet. Sounds very similar to a bug fix listed in HCP 7.1 release notes "HCP-23866"...which is the release I am already running so the fix should be in...

https://unc01.hcp.its.unc.edu/HTSF/Public/testfile.txt?AWSAccessKeyId=cm9ieg%3D%3D&Expires=1444395582&Signature=61uGZh5%2FN0nN020%2BjtsIEvSkhqc%3D



When within the subnet / domain the above HCP link works correctly; displaying "This is a test file"

 


When outside the subnet / domain the HCP reports authentication errors. We receive 403 errors:


HTTP/1.1 403 Forbidden
Date: Thu, 24 Sep 2015 14:04:03 GMT
Set-Cookie: HCP-Last-Domain=;Path=/;Domain=hcp.its.unc.edu;Expires=Thu, 01-Jan-1970 00:00:00 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Server: HCP V7.1.0.10
Content-Encoding: gzip
Content-Length: 0

Outcomes