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

Add /login/status/{aid} endpoint #26

Open
2 of 3 tasks
2byrds opened this issue Aug 15, 2024 · 0 comments
Open
2 of 3 tasks

Add /login/status/{aid} endpoint #26

2byrds opened this issue Aug 15, 2024 · 0 comments
Assignees

Comments

@2byrds
Copy link
Collaborator

2byrds commented Aug 15, 2024

Add /login/status/{aid} endpoint indicates if the LAST user login status.
Note the the verifier has this authorization endpoint, which is a start but more information should be provided back through the api:

This call requires signed headers from the same ID because no other user should be able to see the login status for this AID.

The status should indicate the LAST login status such as:

  • If the user tries to make the call without signed headers, the error message should say they need to sign headers.
  • If the last login was a failure then the signed headers won't validate, so the error message should indicate that the user needs to login with a valid ECR credential.
  • If the user has submitted a login request with a valid ECR credential and calls this endpoint with valid signed headers then the response should contain a status with details about the LAST login, including the JSON form of the CESR, see Supply the 'raw' JSON version of the CESR, as part of the login success response vlei-verifier#35

There should be tests for all these scenarios for this endpoint, as well as multiple calls and a mixture of calls.

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

No branches or pull requests

2 participants