<?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: eDirectory as an auth source ITATS307E Parameter conflict error in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/edirectory-as-an-auth-source-itats307e-parameter-conflict-error/m-p/1300126#M3647</link>
    <description>&lt;P&gt;so it turns out, after a few more tests, that the CN value was multivalued - which isn't currently supported by CyberArk - we had to change to an alternate value, which was just a single value duplication of the base CN for this customer - and we're now able to authenticate - nice &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 15 Aug 2018 14:00:48 GMT</pubDate>
    <dc:creator>Hammond</dc:creator>
    <dc:date>2018-08-15T14:00:48Z</dc:date>
    <item>
      <title>eDirectory as an auth source ITATS307E Parameter conflict error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/edirectory-as-an-auth-source-itats307e-parameter-conflict-error/m-p/1300125#M3646</link>
      <description>&lt;P&gt;When configuring edirectory as an Auth source, the client has replaced the LogonUserName field to be a CN, not UID - updating this field, I now receive ITATS701E, ITATS307E - there's nothing in the messaging and responses guide reflecting 307E - but the ITALOG says it's a parameter conflict. Directory Mapping for groups seems to work as expecting - searching for the vault groups by cn=Vault* lists only the groups relevant here, but when searching for users, even with "VaultUsers" specified in the mapping, all users are listed, not just those in the group - could this be the conflict - and if so, how do I resolve it?&lt;/P&gt;</description>
      <pubDate>Wed, 15 Aug 2018 10:31:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/edirectory-as-an-auth-source-itats307e-parameter-conflict-error/m-p/1300125#M3646</guid>
      <dc:creator>Hammond</dc:creator>
      <dc:date>2018-08-15T10:31:46Z</dc:date>
    </item>
    <item>
      <title>Re: eDirectory as an auth source ITATS307E Parameter conflict error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/edirectory-as-an-auth-source-itats307e-parameter-conflict-error/m-p/1300126#M3647</link>
      <description>&lt;P&gt;so it turns out, after a few more tests, that the CN value was multivalued - which isn't currently supported by CyberArk - we had to change to an alternate value, which was just a single value duplication of the base CN for this customer - and we're now able to authenticate - nice &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Aug 2018 14:00:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/edirectory-as-an-auth-source-itats307e-parameter-conflict-error/m-p/1300126#M3647</guid>
      <dc:creator>Hammond</dc:creator>
      <dc:date>2018-08-15T14:00:48Z</dc:date>
    </item>
  </channel>
</rss>

