<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Claim not present in .Net]]></title><description><![CDATA[<p dir="auto">Hi folks,</p>
<p dir="auto">After FusionAuth login, I don't have role claims in the .Net Identity. I use the <strong>.Net+React POC</strong> found here<br />
<a href="https://github.com/FusionAuth/fusionauth-example-asp-net5-react" rel="nofollow ugc">https://github.com/FusionAuth/fusionauth-example-asp-net5-react</a></p>
<p dir="auto">This problem is similar to this post<br />
<a href="https://fusionauth.io/community/forum/topic/1485/role-claims-issue-with-openidconnect-netcore5">https://fusionauth.io/community/forum/topic/1485/role-claims-issue-with-openidconnect-netcore5</a><br />
However not exactly the same, I use both .Net and React, no razor pages. The solution of the post above doesn't work because <code>AddOpenIdConnect ... OnMessageReceived</code> is never called. Not sure it's normal.</p>
<p dir="auto">As I see things in the <strong>.Net+React POC</strong>, they handle everything in the Session, they don't get anything special in <code>HttpContext.User.Identity</code> , is it normal ?<br />
Does it mean we can't have Role Claims when using a .Net + React solution ? I would expect the JWT token to convert into a proper .Net Identity.</p>
<p dir="auto">If anyone can get Role Claims in the <strong>.Net+React POC</strong>, please tell how</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2164/claim-not-present-in-net</link><generator>RSS for Node</generator><lastBuildDate>Sun, 17 May 2026 21:15:11 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/2164.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 30 Aug 2022 06:49:12 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Claim not present in .Net on Wed, 07 Sep 2022 15:16:51 GMT]]></title><description><![CDATA[<p dir="auto">Claim based authorization checks are declarative - the developer embeds them within their code, against a controller or an action    192.168.l.254 within a controller, specifying claims which the current user must possess, and optionally the value the claim must hold to access the requested resource.Claims are a set of information stored in a key – value pair form. Claims are used to store information about user like full name, phone number, email address.... and the most important thing is that you can use claims as a replacement of roles, that you can transfer the roles to be a claim for a user</p>
]]></description><link>https://fusionauth.io/community/forum/post/5454</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/5454</guid><dc:creator><![CDATA[sophiaab98]]></dc:creator><pubDate>Wed, 07 Sep 2022 15:16:51 GMT</pubDate></item><item><title><![CDATA[Reply to Claim not present in .Net on Tue, 06 Sep 2022 18:04:30 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/2017">@lionel-selosse</a> addressed in a related/duplicate thread.</p>
<p dir="auto"><a href="https://fusionauth.io/community/forum/topic/2163/claim-not-present-in-net">https://fusionauth.io/community/forum/topic/2163/claim-not-present-in-net</a></p>
]]></description><link>https://fusionauth.io/community/forum/post/5450</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/5450</guid><dc:creator><![CDATA[joshua]]></dc:creator><pubDate>Tue, 06 Sep 2022 18:04:30 GMT</pubDate></item></channel></rss>