Re: [thredds] Pydap authentication problems

• To: thredds@xxxxxxxxxxxxxxxx
• Subject: Re: [thredds] Pydap authentication problems
• From: Jim Fluke <james.fluke@xxxxxxxxxxxxx>
• Date: Tue, 15 Oct 2024 10:44:30 -0600
• Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=colostate.edu; dmarc=pass action=none header.from=colostate.edu; dkim=pass header.d=colostate.edu; arc=none
• Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=mYwcINY6JgEaCU353RzFUgmvejk4HrOTv4s4p1lHZQQ=; b=Pnayx/fXMyJ3XVV9tTcTRTthJq3iNgiJWpnqpjcFvDtz5vwkWChrO+tGVD2sqB8PwRpEn0L/UmQI6cRYecR0h/Ew+fj0dgrL1nhpnZ7+z/KqajfWNk6CmwzhB1Pv6yVb9yzP1uEe3fl9/pFJkTYmsdMEEgLa/+utCgl+HuQ//HeQrd7rGP69InxxERoDDJjX6mXNbQG25E+4mv9oPGW0PaC0glEuPjlJeI3HrXur8U8Vty7femF2xwRzEqRFmV44CpsgX+HhO9+qf33NgzEsyb2z2QQmo7SnJ2IX2XO6iNI2QErHhawWJuwnmB2QNfbF9TfyeeBmBlH1QfPcMB+j5w==
• Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=b8W3BY2YuUtX783OliW5Xr+jtDkV3xJUkLmfuikKK+0M/EQLGikZ+wBYwU5oHNED9aoE1M4P+9a8a8sS804bCKAE6aABU+b4zLwqrZW08kdo6k/4m/PLn3+oIsgMOa1hoNKtgm0a5L/b82WLR5f46Dkqhv8qMvFJkn8sD9g/eo9kVUaiHXysHqfSfrZC80kL1TyK1x/cGXBg9p6TElomBQL3cBNgojw23A95Clsl+zL0h7byvixEYMxR0Ff3HdYhIKabF+g3otURRmggJ1k3Ua+s1vseBN8LS7+s3vwL2m/R2bXO8GWptwkZXLm6sxdoTkW0FT8CPhQjzn/k3Zrhbw==
• Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=colostate.edu;

Miguel,

Thanks for the reply, and to James Gallagher too!

I'll switch this over to the pydap project its mailing list.

Jim


On 10/11/24 16:02, Miguel Jimenez wrote:

*** Caution: EXTERNAL Sender ***

Hi all!

Just joined this mailing list, and catching up with stuff about pydap and tds. I am actively developing pydap, and updating the documentation. I have migrated the documentation to GitHub pages. And while reading through this thread (and another one about pydap authentication), I was curious about where it said that the username/password could be added to the url . Very interesting approach! I found the source of it, the old pydap documentation. I recently started updating pydap, and its documentation .

In the updated Pydap documentation you can find a particular examples on authentication with username, and with tokens as well. The documentation is built using executable notebooks.

Basic Authentication — PyDAP tutorial <https://pydap.github.io/pydap/notebooks/Authentication.html> pydap.github.io <https://pydap.github.io/pydap/notebooks/Authentication.html>

        <https://pydap.github.io/pydap/notebooks/Authentication.html>

<https://pydap.github.io/pydap/notebooks/Authentication.html>

 I am still curious about adding the username/password to the url. Perhaps internally pydap used to parse that information before my time? I never knew about it...

Anyways, I suggest to bring this issue on PyDAP's GitHub repository. And we can continue the conversation there. I also follow the updated documentation (url above).

PS - I have updated PyDAP and the new version 3.5 is compatible with numpy >=2.0.

Cheers,
Miguel

_______________________________________________
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/

• References:
  • [thredds] Pydap authentication problems
    • From: Miguel Jimenez