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.

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

[uss_qualifier] DSS0030 token validation scenario #340

Merged
merged 1 commit into from
Nov 14, 2023

Conversation

Shastick
Copy link
Contributor

This is an almost direct port of the old test_token_validation.py v1 scenario, but it supports both versions of the standard.

There is the possibility for also testing the endpoints for searching ISAs, which I can do in a later PR.

Comment on lines +577 to +581
# TODO confirm that we can consider the display provider scope as a 'read only scope'
if scope_intent == "read":
return v22a.constants.Scope.DisplayProvider
else:
return v22a.constants.Scope.ServiceProvider
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as the tests are concerned, the DisplayProvider scope indeed prevents any mutation or deletion. In my understanding of the standard, a Display Provider is indeed not supposed to register an ISA, but I'd just want this to be confirmed by a second opinion.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed -- a DisplayProvider is allowed to create and manage Subscriptions, but is not providing identification service, and therefore may not create nor manage Identification Service Areas.

@Shastick Shastick marked this pull request as ready for review November 13, 2023 16:45
@BenjaminPelletier BenjaminPelletier merged commit 6409160 into interuss:main Nov 14, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants