Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[EOEPCA/IAM] Refine EOAPI protection (Data Access/ Resource Discovery) #72

Open
w-scho opened this issue Jan 14, 2025 · 0 comments
Open

[EOEPCA/IAM] Refine EOAPI protection (Data Access/ Resource Discovery) #72

w-scho opened this issue Jan 14, 2025 · 0 comments
Assignees
@w-scho
Milestone
Q4 - Release 2.0

Comments

@w-scho
Copy link
Collaborator

w-scho commented Jan 14, 2025 •
edited
Loading

The STAC API subroute has to be refined further, because not all non-GET requests should be protected. This refinement has been moved to Q4 and will be handled in a separate ticket.
This is a follow-up ticket of #42.
See also EOEPCA/resource-discovery#101
and follow-up ticket EOEPCA/resource-discovery#106
@w-scho w-scho added this to the Q4 - Release 2.0 milestone Jan 14, 2025
@w-scho w-scho changed the title [EOEPCA/IAM] Refine EOAPI protection [EOEPCA/IAM] Refine EOAPI protection (Data Access/ Resource Registration) Jan 14, 2025
@w-scho w-scho self-assigned this Jan 14, 2025
@w-scho w-scho changed the title [EOEPCA/IAM] Refine EOAPI protection (Data Access/ Resource Registration) [EOEPCA/IAM] Refine EOAPI protection (Data Access/ Resource Discovery) Jan 14, 2025
@w-scho w-scho changed the title [EOEPCA/IAM] Refine EOAPI protection (Data Access/ Resource Discovery) [EOEPCA/IAM] Refine EOAPI protection (Data Access/ Resource Discovery)Mario_Schomakers Jan 20, 2025
@w-scho w-scho changed the title [EOEPCA/IAM] Refine EOAPI protection (Data Access/ Resource Discovery)Mario_Schomakers [EOEPCA/IAM] Refine EOAPI protection (Data Access/ Resource Discovery) Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@w-scho w-scho

Labels
None yet
Projects
None yet
Milestone
Q4 - Release 2.0
Development

No branches or pull requests
1 participant
@w-scho