Skip to main content

Application cache login issues🔵

Report an IssueLogin/RegistrationClient PortalHigh Priority

Multiple users (internal for now) are running into an authentication issue where the user data gets cached in local storage and cannot be cleared without manually clearing out the users browser app cache.

This additionally causes a side affect where the user is then directed to the Client Portal login screen.

This also creates a 3rd side affect where after the user logs in through the Client Portal screen they lose Super Admin access and are treated like a normal user that can only access assigned companies

I will begin investigation on this immediately

We do have a temporary work around that has a high success rate for fixing this issue:

  • Login to Prodify through the login screen (this works regardless of client portal vs. normal login)

  • After you’ve logged in, press f12 (or fn+f12) to bring up the browser console

  • Look for the application tab and then follow the numbered steps below

  • Reach out to me (Nicholas) on teams if you need help or this does not work

Posted by Nicholas Vail ·
Status: Completed3 comments

Log in to comment and vote

Comments3

  • Nicholas Vail

    Team•

    May 1

    Hey @Steve it was a systemic issue with how the login process worked from the client portal screen and with how we stored whether the user should see the client portal or normal login screen for Prodify. From what I can see this was only an internal issue and did not affect clients, there was a separate token issue that did affect clients that should also be fixed as part of this.

    I added new backend unit testing to our login methods and I will coordinate with Svitlana to see if we can setup more client login testing

  • Steve

    •

    Apr 23

    @Nicholas Vail - flagging again as this keeps coming up in my internal discussions as an ongoing issue. Few questions

    - Do we know the cause / have a fix? Is it systemic vs an anomaly?
    - Do we know if this is an internal only issue, or could affect clients as well?
    - Should we look into updating login testing procedures to catch future issues early?

  • Steve

    •

    Apr 21

    @Nicholas Vail - flagging for you as you look into this. Is this a regression or a new issue? If regression, should we align the fix with Svitlana’s testing processes to catch future issues? Thanks!