Authentication

[kkenjeres]

Value proposition

As a user I want to be able to login on the page and get access to all functions of the app as authorized user.

Description

Acceptance criteria

• [ ] Display login button
• [ ] By clicking login user are able to sing in with their GitHub account
• [ ] All users are allowed to browse games via home page, dice game, or search page
• [ ] If the user clicks on profile page without signing in they will be asked to do so
• [ ] Authorized user can edit and delete the games they created anywhere on the app
  • [ ] Delete and edit buttons only show up on the games they created
  • [ ] The profile page shows the user information and the games they created

Tasks

• [ ] Initialize O-Auth Provider Setup auth routes
• [ ] Create Login Logic display user data
• [ ] Use session to restrict API access
• [ ] Conditionally display secured routes / UI elements
• [ ] use userData to personalize data / displayed content

[F-Kirchhoff]

Hey! please add concrete AC for what in the beviour changes compared to previous this user story:

• how are not logged in users restricted?
• which routes are accessible, which not?
• which elements are displayed after logging in, which are hidden before?

[Roland-Hufnagel]

Looks good to me.