<?xml 
version="1.0" encoding="utf-8"?>
<rss version="2.0" 
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
>

<channel xml:lang="en">

	<title>Monitoring the state of authentication and Single Log Out (SLO) - comments</title>
	<link>https://oa.dnc.global/Monitoring-the-state-of-authentication-and-Single-Log-Out-SLO.html</link>
	<description>
The purpose of the authentication status monitoring is to synchronize the local connection of an application with the corresponding access token. Introduction OAuthSD, following OAuth 2.0, considers that the end user is connected to an application as long as the associated access token is valid. There is no &#034;naturally&#034; direct relationship between this token and the local connection state of an application. Each application will have to set up a monitoring, client side, in order to: &#8211; (&#8230;)
</description>
	<language>en</language>
    <generator>SPIP - www.spip.net</generator>

	<image>
		<title>Monitoring the state of authentication and Single Log Out (SLO)</title>
		<url>https://oa.dnc.global/local/cache-vignettes/L128xH128/arton136-5bed0.png?1794159869</url>
		<link>https://oa.dnc.global/Monitoring-the-state-of-authentication-and-Single-Log-Out-SLO.html</link>
		<height>128</height>
		<width>128</width>
	</image>






</channel>

</rss>
