New auth strategy: token-only

[mfisher87]

Related: #415, #479

Should we provide a method of persisting tokens as well? Should bearer token become the default strategy?

From Hackday meeting 2024-10-15: Luis and Matt agree it should be the default strategy.

[battistowx]

This would be awesome to have, instead of creating a requests query to the CMR API

[mfisher87]

@battistowx @asteiker I feel this feature should really be prioritized before 1.0. I think we need a good way to keep track of these things, so I created a milestone and added this issue to it. I'm not attached to this solution, just feel we need something and want to get the discussion going :) ETAFTP!

There was another issue I was also thinking should be completed before 1.0, and I forgot what it was. I'll find it at some point and add it to the milestone.

[fwfichtner]

First of all thanks for this library, it is very helpful for us! I have a question which is touching this issue. When we are doing earthaccess.search_data() we are login in via environment variables. So far so good, under https://urs.earthdata.nasa.gov/users/username/user_tokens we can see that two new tokens are created. I guess these are CMR Tokens? However, these tokens expire after 2 months and are not re-created and when we continue to use earthaccess we are getting RuntimeError('{"errors":["Token [Bearer eyJXXXI4SIQ] has expired. Note the token value has been partially redacted."]}'. This is solved by just deleting the Bearer Tokens, which triggers a re-creation.

[mfisher87]

Hm. When there are two tokens, the code is supposed to revoke and re-generate a token:

earthaccess/earthaccess/auth.py

Lines 165 to 180 in 7a79ea5

	if len(self.tokens) == 2:
	resp_revoked = self._revoke_user_token(self.token["access_token"])
	if resp_revoked:
	resp_tokens = self._generate_user_token(
	username=self.username, password=self.password
	)
	if resp_tokens.ok:
	self.token = resp_tokens.json()
	self.tokens[0] = self.token
	logger.debug(
	f"earthaccess generated a token for CMR with expiration on: {self.token['expiration_date']}"
	)
	return True
	else:
	logger.info(resp_tokens)
	return False

cc @betolink

[betolink]

Token regeneration is not automatic, actually is not part of the top level API. It could be automatic if we encounter an expired token, as of now one can do this:

import earthaccess

auth = earthaccess.login()

auth.refresh_tokens()

[mfisher87]

Ah cool. Looks like we just need a bit of glue code to automate it :) Thanks, @betolink !

[fwfichtner]

I had a look to support with a PR, but must admit that I struggle to understand what is going on.

If I delete the tokens manually they are re-generated, no problem, however and not changing anything I sometimes end up having three working tokens (even though earthaccess and the https://urs.earthdata.nasa.gov/users/username/user_tokens expect only two (I can see 3 tokens in the UI). Maybe that happens through some kind of race condition.

[battistowx]

Would it be better to use find_or_create_token? We've used that here with no issues: https://github.com/nasa/gesdisc-tutorials/blob/main/notebooks/How_To_Download_a_Spatial_and_Variable_Subset_of_Level_1B_Data_Using_OPeNDAP.ipynb

[chuckwondo]

Would it be better to use find_or_create_token? We've used that here with no issues: https://github.com/nasa/gesdisc-tutorials/blob/main/notebooks/How_To_Download_a_Spatial_and_Variable_Subset_of_Level_1B_Data_Using_OPeNDAP.ipynb

Yes, indeed, you beat me to the punch.

And in case anybody is wondering, that endpoint is implemented to automatically deal with expired tokens, such that it always returns an active token (automatically generating one and returning it, if you only have expired tokens at the time of the request).