Among the features missing in the backend ( #7 , #2), we might be able to use an external JavaScript component.
Most of those are already handled sso.js at postBackend, to a point where the backend can answer (we can configure it through callbackUri).
Backend should return either postSuccessStatusValue, postLogoffStatusValue, or alreadyHasSessionStatusValue.
On 2014-09-29, 2:35 PM, Randall Leeds wrote:
The javascript and the backend for the notes-server authentication are each in just one small file.
What we need is a /recover route on the backend and we need to hook up your
sso script, which is already being loaded but just not called. Probably, we
want to call it inside our checkAuthorization function and then submit
the session recovery token to a /recover route on the backend.
My assumption is that sso.js could have {callbackUri: 'https://notes.webplatform.org/recover'}.
tilgovi
commented
9 years ago
Idea
Have H to work with webplatform’s sso.js.
Notes
Among the features missing in the backend ( #7 , #2), we might be able to use an external JavaScript component.
Most of those are already handled sso.js at
postBackend, to a point where the backend can answer (we can configure it throughcallbackUri).Backend should return either
postSuccessStatusValue,postLogoffStatusValue, oralreadyHasSessionStatusValue.My assumption is that
sso.jscould have{callbackUri: 'https://notes.webplatform.org/recover'}.