{"id":1804,"date":"2018-03-28T06:43:58","date_gmt":"2018-03-28T13:43:58","guid":{"rendered":"https:\/\/self-issued.info\/?p=1804"},"modified":"2018-03-28T06:43:58","modified_gmt":"2018-03-28T13:43:58","slug":"what-does-logout-mean","status":"publish","type":"post","link":"https:\/\/self-issued.info\/?p=1804","title":{"rendered":"What Does Logout Mean?"},"content":{"rendered":"

\"OAuth<\/span>Digital identity systems almost universally support end-users logging into applications and many also support logging out of them. But while login is reasonable well understood, there are many different kinds of semantics for “logout” in different use cases and a wide variety of mechanisms for effecting logouts.<\/p>\n

I led a discussion on the topic “What Does Logout Mean?” at the 2018 OAuth Security Workshop<\/a> in Trento, Italy, which was held the week before IETF 101<\/a>, to explore this topic. The session was intentionally a highly interactive conversation, gathering information from the experts at the workshop to expand our collective understanding of the topic. Brock Allen<\/a> — a practicing application security architect (and MVP for ASP.NET\/IIS) — significantly contributed to the materials used to seed the discussion. And Nat Sakimura<\/a> took detailed notes to record what we learned during the discussion.<\/p>\n

Feedback on the discussion was uniformly positive. It seemed that all the participants learned things about logout use cases, mechanisms, and limitations that they previously hadn’t previously considered.<\/p>\n

Materials related to the session are:<\/p>\n