Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-28296

Squareone: demonstrate logging in with Gafaelfawr from the landing page

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      From the squareone-based landing page we want users to be able to log in, and based on that, gain access to personalized features (TDB).

      The purpose of this story is to demonstrate authenticating with Gafaelfawr from the next.js application, and determine whether auth should be done client-side, server-side, or both.

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-28242 Set up next.js application for next-gen RSP landing page

          • Done

            Activity

            Hide
            Permalink
            jsick Jonathan Sick added a comment -

            This ticket demonstrates a login button, user settings menu while logged in, and the ability to log out.

            • useLogin hook to get login information (or not, if the user isn't logged in).
            • currentUrl hook to get the current page's URL based on the next router. Useful for redirects from the login page.
            • Login component that determines whether the user in logged in, and thus either displays a "log in" link or a User settings menu.
            • The UserMenu component is a proof-of-concept of a drop-down menu that provides access to a user's info and settings. This uses the Menu Button from React UI.
            • Mocked the /login, /logout and /auth/api/v1/user-info pages and endpoints from Gafaelfawr. The Next.js server holds onto the "logged in" user information in memory. This functionality is only visible during development; the Science Platform's ingress will prevent these mocks from being used in production
            • Added server-only configuration to maintain the HTTP protocol configuration (useful for mocked development).
            Show
            jsick Jonathan Sick added a comment - This ticket demonstrates a login button, user settings menu while logged in, and the ability to log out. useLogin hook to get login information (or not, if the user isn't logged in). currentUrl hook to get the current page's URL based on the next router. Useful for redirects from the login page. Login component that determines whether the user in logged in, and thus either displays a "log in" link or a User settings menu. The UserMenu component is a proof-of-concept of a drop-down menu that provides access to a user's info and settings. This uses the Menu Button from React UI. Mocked the /login , /logout and /auth/api/v1/user-info pages and endpoints from Gafaelfawr. The Next.js server holds onto the "logged in" user information in memory. This functionality is only visible during development; the Science Platform's ingress will prevent these mocks from being used in production Added server-only configuration to maintain the HTTP protocol configuration (useful for mocked development).

              People

              Assignee:
              jsick Jonathan Sick
              Reporter:
              jsick Jonathan Sick
              Watchers:
              Jonathan Sick
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.