SWC-6533 #5539
SWC-6533 #5539
Conversation
… login instead of showing it here
| ); | ||
| hostName2OneSageSite.put( | ||
| "portal-dev.dev.sagebase.org", | ||
| "https://accounts-dev.dev.sagebase.org/?appId=dev.synapse.org" |
There was a problem hiding this comment.
Does not yet exist, see IT-3848 and PORTALS-3203
| hostName2OneSageSite.put( | ||
| "localhost", | ||
| "http://localhost:3000/?appId=localhost" | ||
| ); | ||
| hostName2OneSageSite.put( | ||
| "127.0.0.1", | ||
| "http://127.0.0.1:3000/?appId=localhost" | ||
| ); |
There was a problem hiding this comment.
Good idea to handle both
| @Override | ||
| public void gotoLoginPage() { | ||
| //tell One Sage to return to the current url | ||
| cookieProvider.setCookie(ONESAGE_REDIRECT_COOKIE_KEY, gwt.getCurrentURL()); |
There was a problem hiding this comment.
ditto feedback from Sage-Bionetworks/synapse-web-monorepo#1252 , consider expiring
| view.setSynAlert(synAlert); | ||
| view.setPresenter(this); | ||
| } | ||
|
|
||
| @Override | ||
| public void onAcceptTermsOfUse() { |
There was a problem hiding this comment.
So if I sign in to OneSage and have not accepted the terms of use, that app already handles prompting today (before new ToS implementation)?
There was a problem hiding this comment.
It should. The ApplicationSessionManager attempts to initialize the session (used in OneSage AppWrapper). In doing so, it tries to get your User Profile, and looks for the "Terms of use have not been signed" error. It sets the ApplicationSessionContext acceptsTermsOfUse value. If this value is false, then in AppInitializer, it will redirect you to /authenticated/signTermsOfUse, showing you the TermsOfUsePage
|
In stack 518, send to One Sage for login! |
update LoginPresenter to often go to the One Sage root page to handle login instead of showing it here