<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: OAuth behavior changed after upgrade to 200.7 in .NET Maps SDK Questions</title>
    <link>https://community.esri.com/t5/net-maps-sdk-questions/oauth-behavior-changed-after-upgrade-to-200-7/m-p/1637848#M13620</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Thank you for reporting this issue!&amp;nbsp; The problem occured when a service-related ArcGISCredential (e.g., credential for a federated service or a hosted service) was loaded from persistence, and then expired or was removed.&amp;nbsp; This caused repeated requests to the wrong server-info URRL, and it became impossible to log into that service again until the app was restarted.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This issue has been fixed in&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://www.esri.com/arcgis-blog/products/developers/announcements/whats-new-in-arcgis-maps-sdks-for-native-apps-200-8" target="_self" rel="nofollow noreferrer"&gt;ArcGIS Maps SDK 200.8.0&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 30 Jul 2025 22:16:47 GMT</pubDate>
    <dc:creator>MatveiStefarov</dc:creator>
    <dc:date>2025-07-30T22:16:47Z</dc:date>
    <item>
      <title>OAuth behavior changed after upgrade to 200.7</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/oauth-behavior-changed-after-upgrade-to-200-7/m-p/1607394#M13486</link>
      <description>&lt;P&gt;After upgrading to 200.7 I am having issues with authentication.&amp;nbsp; I basically now going to a non-stop loop of being asked to login.&amp;nbsp; Logging shows it is the same exact service that is being requested in the ChallengeHandler.&lt;/P&gt;&lt;P&gt;My 200.6 version of the app works as expected&lt;/P&gt;&lt;P&gt;My process is to use the&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="csharp"&gt;await ArcGISPortal.CreateAsync(new Uri(_portalUrl), true);&lt;/LI-CODE&gt;&lt;P&gt;to log into Portal.&amp;nbsp; In 200.6 that is all that is required and then other services load properly.&lt;/P&gt;&lt;P&gt;In 2007 I connect to the portal, I can see valid tokens in AuthenticationManager, but if I try to query a layer I am presented with the authentication dialog over and over&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Apr 2025 19:01:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/oauth-behavior-changed-after-upgrade-to-200-7/m-p/1607394#M13486</guid>
      <dc:creator>JoeHershman</dc:creator>
      <dc:date>2025-04-18T19:01:12Z</dc:date>
    </item>
    <item>
      <title>Re: OAuth behavior changed after upgrade to 200.7</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/oauth-behavior-changed-after-upgrade-to-200-7/m-p/1637848#M13620</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Thank you for reporting this issue!&amp;nbsp; The problem occured when a service-related ArcGISCredential (e.g., credential for a federated service or a hosted service) was loaded from persistence, and then expired or was removed.&amp;nbsp; This caused repeated requests to the wrong server-info URRL, and it became impossible to log into that service again until the app was restarted.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This issue has been fixed in&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://www.esri.com/arcgis-blog/products/developers/announcements/whats-new-in-arcgis-maps-sdks-for-native-apps-200-8" target="_self" rel="nofollow noreferrer"&gt;ArcGIS Maps SDK 200.8.0&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jul 2025 22:16:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/oauth-behavior-changed-after-upgrade-to-200-7/m-p/1637848#M13620</guid>
      <dc:creator>MatveiStefarov</dc:creator>
      <dc:date>2025-07-30T22:16:47Z</dc:date>
    </item>
  </channel>
</rss>

