Presentation Request explorer initial concept #514
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Lucas ONeil <[email protected]>
loneil
force-pushed
the
feature/presReqExplorer
branch
from
2becfe0 to
f3f7f0b
Compare
esune
approved these changes
May 10, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A very simple version of the Presentation Request Explorer concept that we can iterate on given feedback from Kim and other planning.
Navigating to
{vcauth url}/ver_configs/explorerloads HTML page. This is a public route."ver_configs" is the same router that the API endpoints are on, can adjust route naming and things later on feedback
The UI is just a Jinja template that takes in the output of fetching all Verification Configs.
Can revisit this stuff as more requirements come, extend to a SPA if needed, etc. Depending on future needs if much more business logic (any authentication, sending requests for create/delete pres reqs, contacting via email, etc etc) is needed then moving to a separate standalone FE app rather than just serving an HTML page from VCAuthN API might work better.