<?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>SaaS and OIDC: a successful marriage thanks to OAuthSD! - comments</title>
	<link>https://oa.dnc.global/SaaS-and-OIDC-a-successful-marriage-thanks-to-OAuthSD.html</link>
	<description>
One of the features that DnC has developed to the highest level with its OAuthSD server is to transmit secure information using the JWT identity signed token (JWS). We describe in this article the application i-Tego SaaS, a software as a service (SaaS) delivery system. In this application, OAuthSD provides OIDC authentication and securely transmits to SaaS applications the parameters relating to end-user' subscriptions. Position of the problem Most SaaS systems integrate the (&#8230;)
</description>
	<language>en</language>
    <generator>SPIP - www.spip.net</generator>

	<image>
		<title>SaaS and OIDC: a successful marriage thanks to OAuthSD!</title>
		<url>https://oa.dnc.global/local/cache-vignettes/L144xH181/arton200-b19db.png?1794175863</url>
		<link>https://oa.dnc.global/SaaS-and-OIDC-a-successful-marriage-thanks-to-OAuthSD.html</link>
		<height>181</height>
		<width>144</width>
	</image>






</channel>

</rss>
