Skip to content

user-story-based-exercises/sew-adv-authentication

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

16 Commits
 
 

Repository files navigation

SEW | ADV | Authentification & Authorization

User Story 1

As a platform hoster, I only want certain users to be able to create, modify, and delete songs, so that there is no misuse amongst users.

Acceptance Criteria

  • A mechanism to login by providing username and password is available.
  • A session token is used to identify the logged in user.
  • The operations create, update, and delete can only be successfully performed by a logged in user.
  • A logout mechanism is also available.

HINT

  • Login: POST request to endpoint /login sending form-data including the properties: username and password
  • You can also use cookies instead of header token
  • You can use this user info within your import.sql: insert into benutzer(id, username, password) values (1, 'hugo', '$2a$10$MkLTGxdivqj427wEbGrwu.Qbx7G.2z.d31xVb1Qe9UCwimEdpqp1a'); -- password

User Story 2

As a song provider, I need to be the only one to edit or delete my songs, so that there is no misunderstanding between different users.

Acceptance Criteria

  • It is checked, that the logged in user is the owner of the song before performing an update or a delete.
  • An appropriate status message is shown to the user.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •