Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T test
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Donghwan Kim
  • test
  • Issues
  • #6

Closed
Open
Created Sep 15, 2017 by Donghwan Kim@donghwanMaintainer0 of 8 tasks completed0/8 tasks

ff

In order to use this service as a user, I want to sign in the service.

Acceptance criteria

APIs should meet the followings:

  • Given an email and a password an unauthenticated user input
    • When the user signs in
      • Then it should find a user whose an email equals to the input email.
        • When it doesn't exist
          • Then it should throw an error.
        • When the one user is found
          • See Aegr fef
  • Given a valid authentication token
    • When the user visits some page or calls some API, where only authenticated users can access
      • Then it should authenticate the user, and issue a new token or update the existing token if it's required.
  • Given an invalid authentication token
    • When the user visits some page or calls some API, where only authenticated users can access
      • Then it should throw an error.
A.
  • Then it should encrypt the input password and compare it with the found user's encrypted password.
    • When they are not the same
      • Then it should throw an error.
    • When they are the same
      • Then it should authenticate the user, issue an authentication token and return it.

You should do:

  • Specify the APIs for the client developer to use.

Note

  • There is no information yet about the expire date of the token.
  • The client might require to allow signing in with other unique field later.
Edited Sep 15, 2017 by Donghwan Kim
Assignee
Assign to
Time tracking