<?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>Verifying the origin of the request received by a resource server - comments</title>
	<link>https://oa.dnc.global/Verifying-the-origin-of-the-request-received-by-a-resource-server.html</link>
	<description>
The transmission of tokens to protected resources implies that the latters are receptive to tokens of any origin. This presents an opportunity for an attacker (a foreign application) to exploit a compromised or stolen token. Once more, the analysis reveals that we are only able to ensure data security in the case of the &#034;Authorization Code&#034; flow. Consideration about the security of token transmission to resource servers (RS) The proposed RFC 6749 standard is quite clear on the need to (&#8230;)
</description>
	<language>en</language>
    <generator>SPIP - www.spip.net</generator>

	<image>
		<title>Verifying the origin of the request received by a resource server</title>
		<url>https://oa.dnc.global/local/cache-vignettes/L93xH94/arton149-a6631.png?1794159869</url>
		<link>https://oa.dnc.global/Verifying-the-origin-of-the-request-received-by-a-resource-server.html</link>
		<height>94</height>
		<width>93</width>
	</image>






</channel>

</rss>
