<?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: ASCP on WebSphere Teething Issues in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ascp-on-websphere-teething-issues/m-p/1318684#M18312</link>
    <description>&lt;P&gt;If you have defined the parameters for AppId and Query but the Credential Provider doesn't recognize them, they might be defined on the wrong level or in the wrong context.&lt;/P&gt;</description>
    <pubDate>Sun, 28 Mar 2021 03:11:01 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2021-03-28T03:11:01Z</dc:date>
    <item>
      <title>ASCP on WebSphere Teething Issues</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ascp-on-websphere-teething-issues/m-p/1318682#M18310</link>
      <description>&lt;P&gt;We are trying to configure an existing 3rd party application to use ASCP in WebSphere 8.5.5. We have completed the application logins configuration, as well as the authentication alias and the name space bindings for AppID and Query. We have updated our datasource accordingly and re-deployed the application. Upon startup we see the following errors in the SystemOut.log:-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SEVERE: CACredProvider - GetEnvValues: exception: Context: iaase00006960CelliPAY-UAT/clusters/em101_cluster, name: cell/persistent/em101_epvaim: First component in name em101_epvaim not found.&lt;/P&gt;&lt;P&gt;SEVERE: CACredProvider - initialize: Both CredFilePath and AppId are not defined. AppId or CredFilePath must be defined to get a password.&lt;/P&gt;&lt;P&gt;SEVERE: CACredProvider - initialize: Query is not defined. Query must be defined to get a password.&lt;/P&gt;&lt;P&gt;SEVERE: CACredProvider - login: could not obtain passwrod object&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any suggestions?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Mar 2020 16:44:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ascp-on-websphere-teething-issues/m-p/1318682#M18310</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2020-03-05T16:44:26Z</dc:date>
    </item>
    <item>
      <title>Re: ASCP on WebSphere Teething Issues</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ascp-on-websphere-teething-issues/m-p/1318683#M18311</link>
      <description>&lt;P&gt;We are facing a similar issues. Does anyone have a resolution?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Mar 2021 12:58:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ascp-on-websphere-teething-issues/m-p/1318683#M18311</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-03-25T12:58:44Z</dc:date>
    </item>
    <item>
      <title>Re: ASCP on WebSphere Teething Issues</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ascp-on-websphere-teething-issues/m-p/1318684#M18312</link>
      <description>&lt;P&gt;If you have defined the parameters for AppId and Query but the Credential Provider doesn't recognize them, they might be defined on the wrong level or in the wrong context.&lt;/P&gt;</description>
      <pubDate>Sun, 28 Mar 2021 03:11:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ascp-on-websphere-teething-issues/m-p/1318684#M18312</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-03-28T03:11:01Z</dc:date>
    </item>
  </channel>
</rss>

