[PAGE] - Login Portal, Device List and Register Pages

[JLefebvre55]

Login Portal

@AdamS260

Reuse the stuff from the CloudClub website. Reskin it with MaterialUI.

Register Page

• Input fields for device ID, friendly name
• Generate key button
• Output text for API key
  • "Copy Field" Button

Device Page

@iWebster28

Device listing and management (certificates, remote control, etc.):

• Device list
  • Status (activity, last ping)
• Certificate creation

[harsimrat99]

@iWebster28 as far as the login functionality is concerned, it has been implemented by Adam and it should work fine. The next step should be to make a successful register device request after the login is successful. I know I mentioned storing the token in local storage but as mentioned by @matt8100, the token is automatically cached for subsequent requests. Although, it is only persistent as long as the page isn't refreshed. After that the user will need to log in again.

[matt8100]

Can you confirm that cookies are being set in browser when logging in? Check the lock symbol in Chrome or developer tools in Firefox. I assume cookie deletion on refresh is not desired behaviour.

[harsimrat99]

Hi Matt,
I have confirmed that the cookies are being set in the browser when logging in. I have also just checked that the cookie is persisting even upon page refreshes.

[harsimrat99]

I believe the problem is for the frontend to figure out how to find if the cookie is already present from a previous request because now we know that cookies are being stored upon a successful login. I think there is a header that can allow exposure of other headers: Access-Control-Expose-Headers

I also checked that document.cookie works with the react app and frontend should be able to check if the cookie exists. @AdamS260 can you please confirm this on your setup as well. As I mentioned, ideally, if the cookie already exists, then the token should be accessible and we would not need to get the user to log in again.

Additionally, if the user clicks logout then the cookie should be deleted so that the user has to login in again the next time.

[AdamS260]

I just tried and there is no cookie being stored whenever I log in.

[harsimrat99]

I just tried and there is no cookie being stored whenever I log in.

Hi @AdamS260 ,
Could you please specify if you used the credentials:'include' option when you logged-in? It would also help if you could please specify which branch you were using to log in.

[AdamS260]

I was using the Login-edits branch and there was no credentials: 'include' option specified. When I tried with that I got an error saying: "The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include' ".

[harsimrat99]

Adam,

Thank you very much for clarifying the test conditions.

There are some updates to the staging branch that should help us mitigate that error. Essentially, Matt's latest edits will allow cross-origin requests will clear away this error. The new CORS routines added to the backend allow us to store cookies when the credentials:'include' directive is added.