-
Notifications
You must be signed in to change notification settings - Fork 16
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
Policy backend API spec #2607
Policy backend API spec #2607
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also see comments in issue.
Will user information also be passed to the backend? If so, what field parameter do they belong in?
@@ -0,0 +1,133 @@ | |||
openapi: 3.1.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no
- request_method | ||
- presentation_submission | ||
- vps | ||
properties: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing the input_desciptor_constraint_id_map
from the introspection endpoint? Could probably use a simpler name here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then the entire id to value mapping would have to be standardised. I think it's too early for a decision on that. With the VPs included, a backend can make a decision.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was under the impression that we would introduce this mapping so other parties do not have to deal with PEX/VC/VP and just check the string value they need extracted from the VC/VP. (makes it easier to start)
Do you still want to add this? If not (or undecided) we should probably remove the map from the introspection endpoint too for now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That'll be an incremental change. We can then also process feedback in the same change.
- request_method | ||
- presentation_submission | ||
- vps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are optional? Most backends probably can't handle PEX/VC/VP
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The first versions might just have to, we'll have to experiment a bit to see what's useful.
"200": | ||
description: | | ||
DID has been found and the scope is supported. | ||
If the scope is supported but no presentation definition is required, the response will be 200 with a presentation definition without any input descriptors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what would the use case for this be?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
public service, like a directory service
@@ -175,10 +175,10 @@ func TestHTTPClient_Authorized(t *testing.T) { | |||
handler := http2.Handler{StatusCode: http.StatusOK} | |||
_, client := testServerAndClient(t, &handler) | |||
|
|||
response, err := client.Authorized(ctx, "http://::1:1", request) | |||
response, err := client.Authorized(ctx, "http://test.test", request) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bad test, uses external resources and assumes test.test won't be available?
Better use the test server and an invalid (local) port?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from wiki
.test is a reserved top-level domain intended for usage in software testing. It is guaranteed to never be registered into the Internet.
an ipv6 address won't work on our CI. A .local
takes a second to (not) resolve.
- request_method | ||
- presentation_submission | ||
- vps | ||
properties: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was under the impression that we would introduce this mapping so other parties do not have to deal with PEX/VC/VP and just check the string value they need extracted from the VC/VP. (makes it easier to start)
Do you still want to add this? If not (or undecided) we should probably remove the map from the introspection endpoint too for now
422e868
to
124df4f
Compare
closes #2606
The specification is required to generate a client for the Nuts node and for policy backends to generate the server API.