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

Auth persistence #49

Open
4 tasks
conorsexton opened this issue Jun 15, 2019 · 0 comments
Open
4 tasks

Auth persistence #49

conorsexton opened this issue Jun 15, 2019 · 0 comments
Labels
decision Requires decision to move forward enhancement New feature or request user story Indicates a full user story (vs. an auxiliary task or sub-task)

Comments

@conorsexton
Copy link
Member

conorsexton commented Jun 15, 2019

User story

As a developer testing microservices, I shouldn’t have to enter my Authorization details for every request, so my workflow for getting new data is simple and efficient.

Acceptance criteria

  • Once authenticated for a given endpoint, user can make multiple requests without re-entering Authorization value
  • Should display visual indication in Request Bar that user is authenticated
  • Authorization expires at expected time (based on response from API)
  • Given a URI on another domain, user must re-enter Authorization details

Notes and questions

  • Should auth. details persist across URIs on the same domain?
  • Should auth. details persist from source to test panel on same domain or URI?
@conorsexton conorsexton added enhancement New feature or request user story Indicates a full user story (vs. an auxiliary task or sub-task) labels Jun 15, 2019
This was referenced Jun 15, 2019
@conorsexton conorsexton added the decision Requires decision to move forward label Jun 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decision Requires decision to move forward enhancement New feature or request user story Indicates a full user story (vs. an auxiliary task or sub-task)
Projects
None yet
Development

No branches or pull requests

1 participant