‹ Home
Exported

TOLOGIX - ISLG App Rebuild

Laura Mindorff, COO at IndustrialHarsh Parikh, Tech Lead at DevITMelissa Cowell, General Manager at IndustrialHiren PatelMonica Martinez, MonolabMarysia RaptisPaul MoonIrit WeinfeldPatrick Harris, Web Designer at IndustrialPiyush Kanpariya, DevITRob Wiesenberg, ContegraRadomir Mladenovic, ContegraKetan Sondarva, Technical Project Manager at DevITStephanie Ducasse, Web Developer at IndustrialAkash Buch +16 others
From the list: ISLG Team Feedback - complete before launch

✔ Problem with auto-IP authentication

Morgan M. added this on
Completed by Morgan M.
Assigned to
Harsh Parikh, Tech Lead at DevIT Harsh P. Melissa Cowell, General Manager at Industrial Melissa C. Naomi Joanis, UX Team Lead at Industrial Naomi J.
Notes
Further to the video below, I have noticed some serious issues with auto-IP authentication that need to be resolved. I know these requirements are currently in UAT, but I wanted to ensure these flagged and addressed.
  1. Speed of auto-IP authentication is too slow. It needs to match the speed of the legacy application (if not faster)
  2. I was getting authenticated into the wrong group account (serious problem)

Comments & Events

Harsh Parikh, Tech Lead at DevIT Harsh Parikh, Tech Lead
Hi Morgan Maguire, CEO Morgan ,

This issue is resolved on both rebuild.islg and staging.islg.
Notified 4 people
Morgan Maguire, CEO Morgan Maguire, CEO
Hi Harsh Parikh, Tech Lead at DevIT Harsh ,

Further to my video below, the IP authentication is working, but it is not operating the way it is in the legacy application. In the legacy application, users are able to go directly to specific pages within the Subscriber site and authentication occurs automatically as they are taken directly to the specific pages. 

Currently, in the new application, if a user puts in a specific URL within the Subscriber site, they are directed to the login page, and then after they login, they are taken to the Subscriber dashboard page, rather than the specific page. 

The following changes need to be implemented when a user is navigating to a specific page within the Subscriber site:
  1. When IP authentication is enabled, authentication occurs on their way to the specific page and they are taken directly to the specific page within the Subscriber site.
  2. When IP authentication is disabled, the user is brought to the login page, and then after the user enters authenticated user credentials, the user is brought directly to the specific page within the Subscriber site.
Notified 4 people
Morgan Maguire, CEO
Morgan Maguire completed this to-do.