Unanswered
Post UUX 4.4.0.94
tecton.actions.navigateTo('ssoDirect.ssoAccount', [{vendorId}, {hostAccountId}]);
Pre UUX 4.4.0.94
tecton.actions.openURL('mobilews/sso/generic/{vendorId}/{hostAccountId}', { requiresToken: true });
Pre UUX 4.4.0.81
tecton.actions.openURL('mobilews/sso/generic/{vendorId}/{hostAccountId}?q2token={q2Token}');
q2Token is the HQ Session ID, which can be retrieved with self.online_session.session_id
40 Views
0
Answers
5 years ago
5 years ago
Mark, could you also pass in other parameters to the SSO Extension along with the session ID? I've got an SSO extension that I'm trying to link from another extension but pass it a variable as well.
— Justin Miller 5 years agoJustin, it does not take additional parameters. I recommend implementing a shared cache setup.The first extension sets a value in the cache and then the second extension (SSO) pulls those values from the known cache location.
— Ryan Hollister 5 years agoAdditionally Justin, make sure the key you use in the cache is unique to that session, so append self.online_session.session_id to the key name. Also probably want to delete/unset it once its been read by the SSO extension.
— Ryan Hollister 5 years ago