Hi, I think Miguel @ OPeNDAP might have some ideas about this. He suggested to me that maybe the PyDAP github repo members might have a solution. I’ve added Miguel to the CC list for this message (he has just joined this list as well). James > On Oct 10, 2024, at 17:59, Jim Fluke <james.fluke@xxxxxxxxxxxxx> wrote: > > Well, I now have https working with user authentication for our TDS website. > But I can't get it to work with pydap in Python. > > I want to thank everyone who responded before, especially Christian Skarby > and Pols Maarten, but I finally realized that I don't need nginx for this. > Configuring the TDS to use our certbot certificate works just fine for the > entire TDS website, including getting subsets of data by selecting the "Get > ASCII" button in the "OPeNDAP Dataset Access Form" after entering credentials > in the authentication pop-up. So that is why I'm starting a new email thread > for the remaining pydap problem. > > The same data file URL that works in the "OPeNDAP Dataset Access Form" does > not work with pydap. The credentials need to be added to the URL for this of > course, and that might be the problem. The URL I'm trying with pydap is: > https://fluke:d1ef3ce7e7c41de74192a362524ad0a460692a222d9dd796ee383b56e446d749$1$d03ce0f88475505a68bd0eb37fa570df8120e59ccf62a4f580a55ad612f695c0e385893fe7205f7c181b221ab49bc817d4a33a2b2bb727fdc0ee3420e7e5b99e@xxxxxxxxxxxxxxxxxxxxxxxxx/thredds/dodsC/cloudsat-data/2B-GEOPROF.P1_R05/2013/180/2013180111833_38146_CS_2B-GEOPROF_GRANULE_P1_R05_E06_F00.hdf > > <mailto:b2bb727fdc0ee3420e7e5b99e@xxxxxxxxxxxxxxxxxxxxxxxxx/thredds/dodsC/cloudsat-data/2B-GEOPROF.P1_R05/2013/180/2013180111833_38146_CS_2B-GEOPROF_GRANULE_P1_R05_E06_F00.hdf> > > This includes the hdf-512 hash value for my password from our > tomcat-users.xml file. Again, this works for website authentication, so I > don't see how there can be a problem with the hash value. But this raises an > exception ending with: > webob.exc.HTTPError: 401 Unauthorized > <!doctype html><html lang="en"><head><title>HTTP Status 401 – > Unauthorized</title><style type="text/css">body > {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b > {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 > {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} > .line > {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP > Status 401 – Unauthorized</h1><hr class="line" /><p><b>Type</b> Status > Report</p><p><b>Description</b> The request has not been applied to the > target resource because it lacks valid authentication credentials for that > resource.</p><hr class="line" /><h3>Apache Tomcat</h3></body></html> > > I've also tried my actual password for this with the same result. > > One thought is that pydap does not know about certbot as a CA whereas firefox > does. > > If you have any ideas about what the problem might be, please let me know. > > Thanks, > Jim > _______________________________________________ > NOTE: All exchanges posted to Unidata maintained email lists are > recorded in the Unidata inquiry tracking system and made publicly > available through the web. Users who post to any of the lists we > maintain are reminded to remove any personal information that they > do not want to be made public. > > > thredds mailing list > thredds@xxxxxxxxxxxxxxxx > For list information or to unsubscribe, visit: > https://www.unidata.ucar.edu/mailing_lists/ — James Gallagher jgallagher@xxxxxxxxxxx
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
thredds archives: