NRT3 tokens not being updated?

[alaroy]

I’m having an issue with downloading data from nrt3 that I’m hoping someone reading this can help with.

When I use a newer earthdata token (expires on 6/9/2025) it fails with a response saying I need to be logged into earthdata:

Code: Select all

$ wget -v --no-use-server-timestamps --timeout=20 -O /scratch/lance-to-fs/MOD03.A2025104.1440.061.2025104154845.NRT.hdf --header "Authorization: Bearer <blah, blah, blah>866WA" https://nrt3.modaps.eosdis.nasa.gov/api/v2/content/archives/allData/61/MOD03/2025/104/MOD03.A2025104.1440.061.2025104154845.NRT.hdf

--2025-04-14 16:28:43--  https://nrt3.modaps.eosdis.nasa.gov/api/v2/content/archives/allData/61/MOD03/2025/104/MOD03.A2025104.1440.061.2025104154845.NRT.hdf
Resolving nrt3.modaps.eosdis.nasa.gov (nrt3.modaps.eosdis.nasa.gov)... 198.118.194.30, 2001:4d0:241a:40c0::30
Connecting to nrt3.modaps.eosdis.nasa.gov (nrt3.modaps.eosdis.nasa.gov)|198.118.194.30|:443... connected.
HTTP request sent, awaiting response... 303 See Other
Location: /profiles/licenses/api/v2/content/archives/allData/61/MOD03/2025/104/MOD03.A2025104.1440.061.2025104154845.NRT.hdf [following]
--2025-04-14 16:28:43--  https://nrt3.modaps.eosdis.nasa.gov/profiles/licenses/api/v2/content/archives/allData/61/MOD03/2025/104/MOD03.A2025104.1440.061.2025104154845.NRT.hdf
Reusing existing connection to nrt3.modaps.eosdis.nasa.gov:443.
HTTP request sent, awaiting response... 302 Found
Location: /oauth/login?redirect=%2Fapi%2Fv2%2Fcontent%2Farchives%2FallData%2F61%2FMOD03%2F2025%2F104%2FMOD03.A2025104.1440.061.2025104154845.NRT.hdf [following]
--2025-04-14 16:28:43--  https://nrt3.modaps.eosdis.nasa.gov/oauth/login?redirect=%2Fapi%2Fv2%2Fcontent%2Farchives%2FallData%2F61%2FMOD03%2F2025%2F104%2FMOD03.A2025104.1440.061.2025104154845.NRT.hdf
Reusing existing connection to nrt3.modaps.eosdis.nasa.gov:443.
HTTP request sent, awaiting response... 302 FOUND
Location: https://urs.earthdata.nasa.gov/oauth/authorize?response_type=code&client_id=sXTOeM-6RH5fuK3TacT_Ag&redirect_uri=https%3A%2F%2Fnrt3.modaps.eosdis.nasa.gov%2Foauth%2Fcallback&state=9U0llT6Cjm1PPSK3QleVbhfyFDEUrZ [following]
--2025-04-14 16:28:44--  https://urs.earthdata.nasa.gov/oauth/authorize?response_type=code&client_id=sXTOeM-6RH5fuK3TacT_Ag&redirect_uri=https%3A%2F%2Fnrt3.modaps.eosdis.nasa.gov%2Foauth%2Fcallback&state=9U0llT6Cjm1PPSK3QleVbhfyFDEUrZ
Resolving urs.earthdata.nasa.gov (urs.earthdata.nasa.gov)... 198.118.243.33, 2001:4d0:241a:4081::89
Connecting to urs.earthdata.nasa.gov (urs.earthdata.nasa.gov)|198.118.243.33|:443... connected.
HTTP request sent, awaiting response... 401 Unauthorized
Authentication selected: Basic realm="Please enter your Earthdata Login credentials. If you do not have a Earthdata Login, create one at https://urs.earthdata.nasa.gov//users/new"
Reusing existing connection to urs.earthdata.nasa.gov:443.
HTTP request sent, awaiting response... 401 Unauthorized

Username/Password Authentication Failed

However when I use an older token (expires on 5/8/2024) it works flawlessly on the exact same system and command:

Code: Select all

$ wget -v --no-use-server-timestamps --timeout=20 -O /scratch/lance-to-fs/MOD03.A2025104.1440.061.2025104154845.NRT.hdf --header "Authorization: Bearer <blah, blah, blah>e8IXA" https://nrt3.modaps.eosdis.nasa.gov/api/v2/content/archives/allData/61/MOD03/2025/104/MOD03.A2025104.1440.061.2025104154845.NRT.hdf

--2025-04-14 16:02:35--  https://nrt3.modaps.eosdis.nasa.gov/api/v2/content/archives/allData/61/MOD03/2025/104/MOD03.A2025104.1440.061.2025104154845.NRT.hdf
Resolving nrt3.modaps.eosdis.nasa.gov (nrt3.modaps.eosdis.nasa.gov)... 198.118.194.30, 2001:4d0:241a:40c0::30
Connecting to nrt3.modaps.eosdis.nasa.gov (nrt3.modaps.eosdis.nasa.gov)|198.118.194.30|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 27197584 (26M) [application/octet-stream]
Saving to: ‘/scratch/lance-to-fs/MOD03.A2025104.1440.061.2025104154845.NRT.hdf’

/scratch/lance-to-fs/MOD03.A2025104.1440.0 100%[========================================================================================>]  25.94M  10.2MB/s    in 2.5s    

2025-04-14 16:02:39 (10.2 MB/s) - ‘/scratch/lance-to-fs/MOD03.A2025104.1440.061.2025104154845.NRT.hdf’ saved [27197584/27197584]

$

Is anyone else experiencing this problem?

Also, could someone from the appropriate orginization please look into it, I emailed MODAPSUSO@lists.nasa.gov about this time yesterday but have only gotten an automated reply (ticket #144916). I just checked and it is still an active problem.

Thank you,
Andrew L.

[LAADS_UserServices_M]

We could not reproduce this issue with a newly generated EDL token. We just tested downloading the same file that you reported an issue with using a newly-generated EDL token, and it worked as expected. Can you provide us with the request IDs of failing requests (on nrt3, not on EDL's side).
For curl if you add the -v option our servers will return a line like this:
Request-ID: <some random string>

And, for wget if you add the -S option.

[alaroy]

Thank you for looking into it! I replied to your email. If I find it is something I'm doing wrong I'll post it here so other people can be less stumped when it comes up

-Andrew L.

[alaroy]

I was able to find the issue with the help of friendly folks at laads-support (thank you guys!)

nrt3 (and nrt4) don't recognize a token unless the earth data account "owning" it has been authorized. To get the authorization you need to log into nrt3 (and nrt4 separately) using your browser and the owning account login credentials.

-Andrew L.