HARMONY-1938: Remove fallback authentication functionality and related code #54
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira Issue ID
HARMONY-1938
Description
In order to support local Harmony development without requiring an Earthdata Login application we needed to make some changes to no longer require OAUTH* environment variables with the EDL app information. As part of that change we're also removing the FALLBACK_AUTHN_ENABLED functionality that has not been used for the past few years which required an EDL client application in order to authenticate using a username and password.
Local Test Steps
Test along with the harmony-1938 branch in the main harmony repo. Make sure that services start correctly when OAUTH* environment variables are not set, and the services can continue to successfully download data.
I used this branch for building the opera-rtc-s1-browse image - https://github.com/chris-durbin/opera-rtc-s1-browse/tree/use-local-harmony-service-lib
use-local-harmony-service-lib
branch.build-service
LOCALLY_DEPLOYED_SERVICES
.bin/restart-services
You can then submit a request: http://localhost:3000/C1259974840-ASF/ogc-api-coverages/1.0.0/collections/all/coverage/rangeset?granuleId=G1260014889-ASF&format=image%2Fpng&skipPreview=true
It will fail when it gets to HyBIG (unless you also update it to use the local service library changes), but you can verify that the service produced the correct outputs by looking at your local s3 artifacts bucket.
PR Acceptance Checklist