<?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[Topics tagged with laravel]]></title><description><![CDATA[A list of topics that have been tagged with laravel]]></description><link>https://fusionauth.io/community/forum/tags/laravel</link><generator>RSS for Node</generator><lastBuildDate>Fri, 10 Jul 2026 17:15:23 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/laravel.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[E-mail field not exists in access token]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3001">@zaalbarxx</a> sorry for the delay. I might be missing it (sorry not a PHP person) but I don't see where that confusion comes into play. I know that some of our docs had to get updated because of a change that we made during our 1.50 release that required to request further details in our scopes request.</p>
<blockquote>
<p dir="auto">This release makes significant changes to the default behavior of new Applications with regard to scopes in OAuth workflows. The database migration will update existing Applications to behave in a backwards compatible manner. See the OAuth <a href="/docs/lifecycle/authenticate-users/oauth/scopes" rel="nofollow ugc">Scopes</a> documentation for more information, in particular the Relationship, Unknown scope policy, and Scope handling policy configurations.</p>
</blockquote>
<p dir="auto"><a href="https://fusionauth.io/docs/release-notes/#version-1-50-0" rel="nofollow ugc">https://fusionauth.io/docs/release-notes/#version-1-50-0</a></p>
<p dir="auto">Let me know if that still isn't making sense, or if there is a spot you were hung up on and I would be happy to update our docs. Or even better feel free to add a PR.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2692/e-mail-field-not-exists-in-access-token</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2692/e-mail-field-not-exists-in-access-token</guid><dc:creator><![CDATA[[[global:former-user]]]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[[How?] Laravel native Auth with FusionAuth]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/507">@chirag</a> have you seen these? <a href="https://fusionauth.io/learn/expert-advice/authentication/login-authentication-workflows/" rel="nofollow ugc">https://fusionauth.io/learn/expert-advice/authentication/login-authentication-workflows/</a></p>
<p dir="auto">Reviewing them and mapping your use case on to them may be helpful.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/695/how-laravel-native-auth-with-fusionauth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/695/how-laravel-native-auth-with-fusionauth</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>