<?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: Query regarding SSO fallback access on tenant in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Query-regarding-SSO-fallback-access-on-tenant/m-p/109811#M6811</link>
    <description>&lt;P&gt;I think you may need to open support ticket and post product IDEA. If this is not supported to use the same domain, it may be problematic to handle such case. &lt;/P&gt;&lt;P&gt;Sebastian &lt;/P&gt;</description>
    <pubDate>Mon, 09 Mar 2020 11:07:48 GMT</pubDate>
    <dc:creator>skrystosik</dc:creator>
    <dc:date>2020-03-09T11:07:48Z</dc:date>
    <item>
      <title>Query regarding SSO fallback access on tenant</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Query-regarding-SSO-fallback-access-on-tenant/m-p/109810#M6810</link>
      <description>&lt;P&gt;We are required to have SSO access federation for our Dynatrace SaaS tenant.&lt;/P&gt;
&lt;P&gt;However, the &lt;A href="https://www.dynatrace.com/support/help/shortlink/manage-users-groups-with-saml#h1-create-a-fallback-user-account-" target="_blank" rel="noopener noreferrer noopener noreferrer noopener noreferrer noopener noreferrer noopener noreferrer noopener noreferrer noopener noreferrer noopener noreferrer"&gt;&lt;STRONG&gt;fallback user account&lt;/STRONG&gt;&lt;/A&gt; pre-requisite states that it is only feasible to have such access to the email id on a&amp;nbsp;&lt;STRONG&gt;different domain&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;Procuring such email ids on a different domain is not feasible as per the organizational standards. Can you please suggest how to mitigate this impediment?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Aug 2022 10:56:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Query-regarding-SSO-fallback-access-on-tenant/m-p/109810#M6810</guid>
      <dc:creator>rswarnka</dc:creator>
      <dc:date>2022-08-31T10:56:55Z</dc:date>
    </item>
    <item>
      <title>Re: Query regarding SSO fallback access on tenant</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Query-regarding-SSO-fallback-access-on-tenant/m-p/109811#M6811</link>
      <description>&lt;P&gt;I think you may need to open support ticket and post product IDEA. If this is not supported to use the same domain, it may be problematic to handle such case. &lt;/P&gt;&lt;P&gt;Sebastian &lt;/P&gt;</description>
      <pubDate>Mon, 09 Mar 2020 11:07:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Query-regarding-SSO-fallback-access-on-tenant/m-p/109811#M6811</guid>
      <dc:creator>skrystosik</dc:creator>
      <dc:date>2020-03-09T11:07:48Z</dc:date>
    </item>
    <item>
      <title>Re: Query regarding SSO fallback access on tenant</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Query-regarding-SSO-fallback-access-on-tenant/m-p/109812#M6812</link>
      <description>&lt;P&gt;We ran into the same thing when SSO was released. We ended up making an exception and using a gmail account created specifically for this with a very long and random password that we store in our key vault. &lt;/P&gt;&lt;P&gt;I completely agree this is not ideal, but it is one way around it. I would highly recommend creating an RFE on this. I see no reason that is obvious as to why something could not be added to the account configuration page to supply a single email even on the same domain as a backup.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 09 Mar 2020 20:10:12 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Query-regarding-SSO-fallback-access-on-tenant/m-p/109812#M6812</guid>
      <dc:creator>larry_roberts</dc:creator>
      <dc:date>2020-03-09T20:10:12Z</dc:date>
    </item>
    <item>
      <title>Re: Query regarding SSO fallback access on tenant</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Query-regarding-SSO-fallback-access-on-tenant/m-p/109813#M6813</link>
      <description>&lt;P&gt;Unfortunately, due to constraints on account access,  I cannot test such configuration. &lt;/P&gt;&lt;P&gt;Thanks for suggestions Larry !&lt;/P&gt;</description>
      <pubDate>Wed, 11 Mar 2020 09:02:36 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Query-regarding-SSO-fallback-access-on-tenant/m-p/109813#M6813</guid>
      <dc:creator>rswarnka</dc:creator>
      <dc:date>2020-03-11T09:02:36Z</dc:date>
    </item>
    <item>
      <title>Re: Query regarding SSO fallback access on tenant</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Query-regarding-SSO-fallback-access-on-tenant/m-p/109814#M6814</link>
      <description>&lt;P&gt;Hmm, may be we could have some mechanism like access keys for such access. &lt;/P&gt;</description>
      <pubDate>Wed, 11 Mar 2020 09:14:31 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Query-regarding-SSO-fallback-access-on-tenant/m-p/109814#M6814</guid>
      <dc:creator>rswarnka</dc:creator>
      <dc:date>2020-03-11T09:14:31Z</dc:date>
    </item>
  </channel>
</rss>

