A/B Testing behind Authentification and Angular routing

[jhirahoka]

Hi guys

I'm having some problems when trying to navigate to an authenticated page on Targets VEC when switching to Compose mode.

My homepage navigates to an external login page, after the user finishes the login process, it  redirects it back to save the provided token in session storage and redirects to the next step via angular routing. (We are using angular 7)

https://domain.com/#/  -> https://domain2.com/#/auth -> https://domain.com/#/token/xxx-xxxx-xxxxxx -> https://domain.com/#/page1

Even though visually my page is rendering https://domain.com/#/page1 the url remains as  https://domain.com/#/token/xxx-xxxx-xxxxxx so when I switch to Compose mode it fails because it tries to use the same token again.

Any clues on how to fix this?

[Andrey_Osadchuk · Accepted solution]

Just an idea, try to create the activity in EEC instead of VEC.

Best wishes,
Andrey Osadchuk | Inspect Launch Implementation, Automate Classifications & Data Sources, Essential Bookmarks