<?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>Definition of OIDC scopes and generalities on their use by applications - comments</title>
	<link>https://oa.dnc.global/Definition-of-OIDC-scopes-and-generalities-on-their-use-by-applications.html</link>
	<description>
The extent of the authorization is defined by the Scopes. This is probably the most open point of the standard and therefore a difficult concept to master for the developer of an application using OpenID Connect. The ability to modulate authorization extent based on the client application and the end user is an exceptionally interesting feature of OAuthSD. We often see in OIDC a simple SSO, but it misses all the power of the device: the JWT identity token combines inseparably and in a (&#8230;)
</description>
	<language>en</language>
    <generator>SPIP - www.spip.net</generator>

	<image>
		<title>Definition of OIDC scopes and generalities on their use by applications</title>
		<url>https://oa.dnc.global/local/cache-vignettes/L144xH124/arton170-ae222.jpg?1794175823</url>
		<link>https://oa.dnc.global/Definition-of-OIDC-scopes-and-generalities-on-their-use-by-applications.html</link>
		<height>124</height>
		<width>144</width>
	</image>






</channel>

</rss>
