[ 
https://issues.apache.org/jira/browse/CLIMATE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260861#comment-16260861
 ] 

Michael Anderson commented on CLIMATE-933:
------------------------------------------

Found this article on Apple's changes in El Capitain (my old mac) and Sierra 
(my new mac):

https://www.thesslstore.com/blog/macos-trusted-root-certificates/

Will check that the issuer for esgf-node.jpl.nasa.gov is always trust.

I notice a 302 error mid way through the error stack.  That 302 is redirecting 
to the esgf login page which would be consistent with not trusting the cert.

> 401 Error On ESGF Download
> --------------------------
>
>                 Key: CLIMATE-933
>                 URL: https://issues.apache.org/jira/browse/CLIMATE-933
>             Project: Apache Open Climate Workbench
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 1.1.0
>            Reporter: Michael Anderson
>
> Running the esgf example or main file in esgf directory produce 401 error.
> 1.  I can log into the esgf web site (i.e. my open ID, user ID and password 
> are good).
> 2.  I am a a member of two groups.  If I take the URL generated by the esgf 
> module and put this directly into my browser, the file downloads.  This 
> confirms both that I am a member of a valid group and the file I am 
> attempting to download exists.
> 3.  credentials.pem gets created in ~/.esg and has content.  Per many 
> suggestions via Google, have deleted and recreated ~/.esg literally dozens to 
> times.  
> 4.  Have also attempted using esg node other than JPL.
> 5.  First attempted on Mac with El Capitain (on which this worked about a 
> year ago).  Upgraded Mac to High Sierra.  Also attempted on a brand new Mac 
> literally out of the package.
> 6.  Openssl 0.9.8 and 1.0.1.  Python 2.7.10
> 7.  Fresh clone from git.  Fresh install of supporting libs:  
> https://cwiki.apache.org/confluence/display/CLIMATE/Installing+OCW+using+the+conda+package+manager



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to