<?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: BROKEN SSO in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201380#M23791</link>
    <description>&lt;P&gt;Here is an official information from the Dynatrace:&lt;/P&gt;
&lt;DIV class="p-rich_text_section"&gt;This message is to inform you that we are aware of an ongoing outage that is impacting our customers. This outage affects all SSO related applications including:&lt;/DIV&gt;
&lt;UL class="p-rich_text_list p-rich_text_list__bullet" data-stringify-type="unordered-list" data-indent="0" data-border="0"&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Tenant access&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Support ticketing system&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Community forums&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Dynatrace University&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="p-rich_text_section"&gt;Data and backend processing is not affected. The root cause is still being investigated and mitigation steps are in progress as we continue to work through this issue. Please follow&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="c-link" tabindex="-1" href="https://dynatrace.status.io/" target="_blank" rel="noopener noreferrer" data-stringify-link="https://dynatrace.status.io/" data-sk="tooltip_parent" data-remove-tab-index="true"&gt;https://dynatrace.status.io/&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;for updates.&lt;/DIV&gt;</description>
    <pubDate>Tue, 03 Jan 2023 17:10:51 GMT</pubDate>
    <dc:creator>MaciejNeumann</dc:creator>
    <dc:date>2023-01-03T17:10:51Z</dc:date>
    <item>
      <title>BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201373#M23786</link>
      <description>&lt;P&gt;FYI, SSO for SaaS Customers&amp;nbsp; are getting a 504 Error - Gateway Time-out&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 15:50:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201373#M23786</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2023-01-03T15:50:48Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201374#M23787</link>
      <description>&lt;P&gt;Update - While SSO is broken, Alert notifications are still being generated. - User UI Access is the only aspect affected.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 15:58:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201374#M23787</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2023-01-03T15:58:53Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201375#M23788</link>
      <description>&lt;P&gt;This will be updated in the status portal ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;updated:&lt;/P&gt;&lt;P&gt;nevermind..&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="rgarzon1_0-1672761791946.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/9202i53B124CD77E218B6/image-size/medium?v=v2&amp;amp;px=400" role="button" title="rgarzon1_0-1672761791946.png" alt="rgarzon1_0-1672761791946.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 16:03:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201375#M23788</guid>
      <dc:creator>rgarzon1</dc:creator>
      <dc:date>2023-01-03T16:03:24Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201377#M23789</link>
      <description>&lt;P&gt;For anyone who doesn't have the Status IO page:&amp;nbsp;&lt;A href="https://dynatrace.status.io/" target="_blank"&gt;https://dynatrace.status.io/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 16:05:10 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201377#M23789</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2023-01-03T16:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201378#M23790</link>
      <description>&lt;P&gt;Hello everybody,&lt;/P&gt;
&lt;P&gt;The status portal is already showing the status of this issue:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://dynatrace.status.io" target="_self"&gt;Dynatrace Saas Status&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;BLOCKQUOTE&gt;&lt;SPAN&gt;We are aware of an issue causing an outage for logging in to our SaaS clusters. We're currently working to resolve this issue and will update here as soon as we have more information. This outage does not affect data processing, and there is no expected data loss. &lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;The SSO team is aware of this issue and already working on a solution. As soon as we have more information, I'll post it here.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 16:26:51 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201378#M23790</guid>
      <dc:creator>MaciejNeumann</dc:creator>
      <dc:date>2023-01-03T16:26:51Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201380#M23791</link>
      <description>&lt;P&gt;Here is an official information from the Dynatrace:&lt;/P&gt;
&lt;DIV class="p-rich_text_section"&gt;This message is to inform you that we are aware of an ongoing outage that is impacting our customers. This outage affects all SSO related applications including:&lt;/DIV&gt;
&lt;UL class="p-rich_text_list p-rich_text_list__bullet" data-stringify-type="unordered-list" data-indent="0" data-border="0"&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Tenant access&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Support ticketing system&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Community forums&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Dynatrace University&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="p-rich_text_section"&gt;Data and backend processing is not affected. The root cause is still being investigated and mitigation steps are in progress as we continue to work through this issue. Please follow&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="c-link" tabindex="-1" href="https://dynatrace.status.io/" target="_blank" rel="noopener noreferrer" data-stringify-link="https://dynatrace.status.io/" data-sk="tooltip_parent" data-remove-tab-index="true"&gt;https://dynatrace.status.io/&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;for updates.&lt;/DIV&gt;</description>
      <pubDate>Tue, 03 Jan 2023 17:10:51 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201380#M23791</guid>
      <dc:creator>MaciejNeumann</dc:creator>
      <dc:date>2023-01-03T17:10:51Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201382#M23792</link>
      <description>&lt;P&gt;The newest information from the&amp;nbsp;&lt;A href="https://dynatrace.status.io" target="_self"&gt;Dynatrace Saas Status&lt;/A&gt;:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;STRONG&gt;[Identified]&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN class="incident_message_details"&gt;Latest update: We are using all resources available to come to a resolution on this accessibility issue, however, the rebuild process is still working on completing. Data is still processeing into respective tenants, and problems/notifications will still be triggered. If you have an API token already set you can reference this page below to access your problems list to not miss any important issues. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.dynatrace.com/support/help/dynatrace-api/environment-api/problems-v2/problems/get-problems-list" target="_blank" rel="noopener"&gt;dynatrace.com/support/help/dynatrace-api/environment-api/problems-v2/problems/get-problems-list&lt;/A&gt;&lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Tue, 03 Jan 2023 18:41:02 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201382#M23792</guid>
      <dc:creator>MaciejNeumann</dc:creator>
      <dc:date>2023-01-03T18:41:02Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201383#M23793</link>
      <description>&lt;P&gt;Access has been restored&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 18:42:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201383#M23793</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2023-01-03T18:42:53Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201384#M23794</link>
      <description>&lt;P&gt;Access is restored but dynatrace.status.io is still all red &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 18:49:46 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201384#M23794</guid>
      <dc:creator>Yosi_Neuman</dc:creator>
      <dc:date>2023-01-03T18:49:46Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201385#M23795</link>
      <description>&lt;P&gt;Not a good start to the year &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 18:55:16 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201385#M23795</guid>
      <dc:creator>Kenny_Gillette</dc:creator>
      <dc:date>2023-01-03T18:55:16Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201390#M23797</link>
      <description>&lt;P&gt;&lt;A href="https://dynatrace.status.io/" target="_self" rel="nofollow noopener noreferrer"&gt;Dynatrace Saas Status&lt;/A&gt;&amp;nbsp;is green again. Here is the latest update:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;STRONG&gt;[Monitoring]&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN class="incident_message_details"&gt;Services have been restored, and you should be able to log in to see your data again. We will continue to monitor this situation to ensure stability as we return to normal usage levels. We appreciate your patience while we worked to resolve this issue and apologize for the inconvenience it caused. &lt;BR /&gt;&lt;BR /&gt;Login was unavailable during these times: 15:26 - 19:00 UTC on 1/3&lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Tue, 03 Jan 2023 19:35:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201390#M23797</guid>
      <dc:creator>MaciejNeumann</dc:creator>
      <dc:date>2023-01-03T19:35:53Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201391#M23798</link>
      <description>&lt;P&gt;Our web and mobile applications that have the OneAgent monitors experienced an authentication outage during the entire Dynatrace outage and only became available once Dynatrace fixed their issue.&amp;nbsp; We didn't expect an agent to impact our systems like this.&amp;nbsp; Did anyone else experience issues with systems monitored by Dynatrace during the outage??&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 20:03:26 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201391#M23798</guid>
      <dc:creator>FixItNow</dc:creator>
      <dc:date>2023-01-03T20:03:26Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201394#M23800</link>
      <description>&lt;P&gt;I think the outage was more than only in the Dynatrace perimeter. I hope we hear the real root cause.&lt;BR /&gt;During the exact same periode the booking system of an european airline, was unavailable.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jan 2023 11:08:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201394#M23800</guid>
      <dc:creator>fstekelenburg</dc:creator>
      <dc:date>2023-01-04T11:08:55Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201395#M23801</link>
      <description>&lt;P&gt;Thanks for the response.&amp;nbsp; Our outage window matched the Dynatrace window so we are going to be pushing for detail on root cause but also confirmation of real impact during their outage&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 20:43:54 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201395#M23801</guid>
      <dc:creator>FixItNow</dc:creator>
      <dc:date>2023-01-03T20:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201396#M23802</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/58341"&gt;@FixItNow&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;We are a Dynatrace partner and have access to multiple client tenants. We did not see any problem from the Dynatrace monitoring, at least until now.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 20:55:12 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201396#M23802</guid>
      <dc:creator>AntonioSousa</dc:creator>
      <dc:date>2023-01-03T20:55:12Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201397#M23803</link>
      <description>&lt;P&gt;Just to share in reply: we did not have any ActiveGate or OneAgent outages during this timeframe. We even went so far as to check the ActiveGate and OneAgent logs themselves - just to see if anything was giving an exception, or retries or errors. We didn't see any issues there at all. From the Kbps throughput on the ActiveGate egress - we knew there was data still flowing.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 20:57:01 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201397#M23803</guid>
      <dc:creator>m3tomlins</dc:creator>
      <dc:date>2023-01-03T20:57:01Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201401#M23805</link>
      <description>&lt;P&gt;From the explanation available at dynatrace.status.io, and emails received, it seems the problem originated in a update to the SSO service. I can't even imagine how that would relate to a problem in Ryanair, as Ryanair seems to be a New Relic client (checked out their RUM data).&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 21:16:15 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201401#M23805</guid>
      <dc:creator>AntonioSousa</dc:creator>
      <dc:date>2023-01-03T21:16:15Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201402#M23806</link>
      <description>&lt;P&gt;BTW, the explanation is consistent with what we observed during the whole episode. Tenants were responding correctly, with multiple objects &amp;amp; XHR being served. We were also able to interact with data through our programs using APIs, both exporting &amp;amp; ingesting data. Also, everything involving alarms kept on flowing, and the suggestion that was put in dynatrace.status.io about using the problem API was very interesting...&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 21:20:16 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201402#M23806</guid>
      <dc:creator>AntonioSousa</dc:creator>
      <dc:date>2023-01-03T21:20:16Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201436#M23811</link>
      <description>&lt;P&gt;must have been a bad coincidence (for me), or use of the same change/maintenance window &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;For a moment I had a flash back to the disruption caused by the Cloudflare outage in June.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jan 2023 11:14:26 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201436#M23811</guid>
      <dc:creator>fstekelenburg</dc:creator>
      <dc:date>2023-01-04T11:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: BROKEN SSO</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201472#M23822</link>
      <description>&lt;P&gt;There are really some strange coincidences out there...&lt;/P&gt;&lt;P&gt;But correlation is not causation &lt;span class="lia-unicode-emoji" title=":face_with_tears_of_joy:"&gt;😂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jan 2023 14:17:10 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BROKEN-SSO/m-p/201472#M23822</guid>
      <dc:creator>AntonioSousa</dc:creator>
      <dc:date>2023-01-04T14:17:10Z</dc:date>
    </item>
  </channel>
</rss>

