Log-out

[tiffany-tang]

When I am using this web-app on another device or someone else is using my device,
I want to log out of my account
So no one else can access my account.

Acceptance Criteria

• To have a 'log out' button

relates to: #5

[iteles]

@Cleop The positioning of this button is TBDiscussed when we get to it 😊

@tiffany-tang This is a feature that I have always felt was very necessary to protect the children's privacy but I'm very curious to see if it even comes up in the user testing on 22-Oct!

[tiffany-tang]

@iteles I put it as priority-3 for the time being as I have some questions regarding GDPR I have yet to ask. It is definitely an important feature for the app.

[tiffany-tang]

@RobStallion Looks fine to me so far

[RobStallion]

@tiffany-tang Great 👍 . If you're happy with this issue then go ahead and close the issue.

[tiffany-tang]

Just tested this again and when I logged out it says "Forbidden".

[RobStallion]

Hey @tiffany-tang. I have not been able to recreate this issue. If you can recreate the issue would you be able to list the steps that you took to get this to happen and open a new issue?

For example, the user you logged in as, if you had logged any emotions that day, etc. Thanks

[tiffany-tang]

@RobStallion
I have retried this on a Motorola phone and Samsung phone with Google Chrome, and on an Iphone8 with Safari for the accounts test1, 2, 3, 4, 5, 6, 7, 8, and test_user. I couldn't re-create this as well. Closing this.

[SimonLab]

@RobStallion I manage to recreate the "forbidden" issue. This is caused when the cookien containing the user session is not valid anymore (you can try to delete it and click on logout)

[Cleop]

@SimonLab - where possible would you be able to open a new issue for bugs that occur once the initial issue has been tested and closed?

[SimonLab]

After a bit more research the "forbidden" error message is the normal logic. It happens when the session is not valid anymore and protect from other people trying to logout users.
Maybe a recent deployment invalidate the current session and it's why the error message appears but I don't think this should occurs once the application is on production