<?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 Skip credentials prompt on NTLM-SSO Fail in Alfresco Forum</title>
    <link>https://connect.hyland.com/t5/alfresco-forum/skip-credentials-prompt-on-ntlm-sso-fail/m-p/3751#M1487</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alfresco Version: Community - 5.1.0 (r127059-b7)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have managed to successfully configure passthru for Share-SSO against our ActiveDirectory. Domain authenticated Users can login without problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem I am faced with now lies with our customer's users, which we create directly in Alfresco. Whenever a non-domain user tries to open our Share-Site, he gets met with a credentials prompt. Using that prompt, it is impossible to login with anything but a domain user.&lt;BR /&gt;&lt;SPAN&gt;Even when using the SSO-bypass from the documentation (&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://our.alfresco.page/share/page/type/login" rel="nofollow noopener noreferrer" target="_blank"&gt;https://our.alfresco.page/share/page/type/login&lt;/A&gt;&lt;SPAN&gt; ), a non-domain user is met with a credentials prompt.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;When canceling the prompt twice, the non-domain user is presented with a blank page (&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://issues.alfresco.com/jira/browse/MNT-15841" rel="nofollow noopener noreferrer" target="_blank"&gt;https://issues.alfresco.com/jira/browse/MNT-15841&lt;/A&gt;&lt;SPAN&gt; like in this case. Although I now see that this seems to have been fixed in the 201612GA version).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is: is it possible to completely skip the credentials-prompt on authentication failure, meaning that external, non-domain users would always just get presented with the normal share login screen? Or is this a limitation of NTLM SSO and we would be better off using another SSO method (for example Kerberos)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Jan 2017 11:58:32 GMT</pubDate>
    <dc:creator>rfras</dc:creator>
    <dc:date>2017-01-19T11:58:32Z</dc:date>
    <item>
      <title>Skip credentials prompt on NTLM-SSO Fail</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/skip-credentials-prompt-on-ntlm-sso-fail/m-p/3751#M1487</link>
      <description>Alfresco Version: Community - 5.1.0 (r127059-b7)I have managed to successfully configure passthru for Share-SSO against our ActiveDirectory. Domain authenticated Users can login without problems.The problem I am faced with now lies with our customer's users, which we create directly in Alfresco. Whe</description>
      <pubDate>Thu, 19 Jan 2017 11:58:32 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/skip-credentials-prompt-on-ntlm-sso-fail/m-p/3751#M1487</guid>
      <dc:creator>rfras</dc:creator>
      <dc:date>2017-01-19T11:58:32Z</dc:date>
    </item>
    <item>
      <title>Re: Skip credentials prompt on NTLM-SSO Fail</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/skip-credentials-prompt-on-ntlm-sso-fail/m-p/3752#M1488</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Simply deploy a second Share instance and do not configure it for SSO. Otherwise there is no way to determine if a user will be able to perform SSO and suppress the popup pre-emptively.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jan 2017 23:37:27 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/skip-credentials-prompt-on-ntlm-sso-fail/m-p/3752#M1488</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2017-01-19T23:37:27Z</dc:date>
    </item>
  </channel>
</rss>

