-
-
Notifications
You must be signed in to change notification settings - Fork 763
Implement Session Management Spec #30
Comments
OIDC board is unsure right now what the right approach is - we will postpone that feature. |
Is there any update on this? I understand that the spec is still a draft, but I think this is required for functionally implementing the implicit flow in a SPA. |
We will implement that at some point - but it does not have a high priority. The spec is actively discussed in the working group right now - expect changes. |
Interesting, am I correct in understanding that without the Does this not prevent use of the implicit flow? |
No - the id token is just the outcome of the authentication process - it is not used to establish a session. The client itself is responsible for creating a session of some sorts. |
I guess I just mean that without support for the Session Management Spec, specifically
I think the first of which is impractical, but I guess option 2 works. |
Expect id tokens to be really short lived in practice - we are defaulting to 5 minutes IIRC.
|
@leastprivilege Now we have the RP initiated logout capability (http://leastprivilege.com/2014/10/14/identityserver-v3-and-post-logout-redirect/) [thank you] that requires the identity token to be maintained by the client in order to pass it back to the OP, are we expecting to have long lived id tokens now, or is 'exp' aspect of validating the token ignored for the logout? |
Expiration is ignored. On 14.10.2014, at 21:40, "Ciaran Jessup" <notifications@github.commailto:notifications@github.com> wrote: Now we have the RP initiated logout capability (http://leastprivilege.com/2014/10/14/identityserver-v3-and-post-logout-redirect/) [thank you] that requires the identity token to be maintained by the client in order to pass it back to the OP, are we expecting to have long lived id tokens now, or is 'exp' aspect of validating the token ignored for the logout? Reply to this email directly or view it on GitHubhttps://github.com//issues/30#issuecomment-59103815. |
OK - session ID and check_session_iframe is implemented on dev |
No description provided.
The text was updated successfully, but these errors were encountered: