<?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: 13.9.1: evoke configuration apply does not activate authenticators defined in conjur.yml in Secrets Management</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management/13-9-1-evoke-configuration-apply-does-not-activate/m-p/1425829#M2264</link>
    <description>&lt;P&gt;Hi @Julien stechele​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you validate the conjur.yml permissions first? Similar to the ones mentioned in this thread&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/question/0D5Vy00003U0Mo4KAF/error-i-info-loading-conjur-config-file-etcconjurconfigconjurym&lt;/P&gt;</description>
    <pubDate>Fri, 09 Oct 2026 08:05:13 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-10-09T08:05:13Z</dc:date>
    <item>
      <title>13.9.1: evoke configuration apply does not activate authenticators defined in conjur.yml</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/13-9-1-evoke-configuration-apply-does-not-activate/m-p/1425828#M2263</link>
      <description>&lt;P&gt;We are migrating authenticator configuration from the deprecated `CONJUR_AUTHENTICATORS` variable to `/etc/conjur/config/conjur.yml`.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The YAML is loaded correctly:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;CODE&gt;evoke configuration show&lt;/CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;reports all authenticators with:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;CODE&gt;authenticators:
 value:
  - authn
  - authn-jwt/...
  - authn-k8s/...
 source: yml&lt;/CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, after running:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;CODE&gt;evoke variable unset CONJUR_AUTHENTICATORS
evoke configuration apply&lt;/CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the local `/info` endpoint reports only:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;CODE&gt;{
 "authenticators": {
  "enabled": ["authn"]
 }
}&lt;/CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Modifying the authenticator list in `conjur.yml` and applying it again does not change the enabled authenticators.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;`evoke configuration apply` outputs:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;CODE&gt;Conjur server reboot initiated. New configuration will be applied.
&amp;nbsp;
...
&amp;nbsp;
Config reload successful
Syslog-ng service restarted.&lt;/CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, unlike `evoke variable set`, it does not show the Conjur, seed, PostgreSQL, or nginx services being stopped and started.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Setting the deprecated variable works immediately:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;CODE&gt;evoke variable set CONJUR_AUTHENTICATORS "&amp;lt;comma-separated-list&amp;gt;"&lt;/CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This performs a full service restart, after which `/info.authenticators.enabled` contains the complete list.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We also observed that:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;CODE&gt;evoke variable unset --no-restart CONJUR_AUTHENTICATORS
evoke configuration apply&lt;/CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;appears successful only while services continue running with the previous variable-derived configuration. After a real restart, the YAML configuration is not reflected in the enabled authenticators.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**Expected behavior**&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;`evoke configuration apply` should restart or reload all required services so that `authenticators` from `conjur.yml` becomes the effective runtime configuration.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please confirm:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Whether YAML-managed authenticators are supported in this appliance version.&lt;/P&gt;&lt;P&gt;2. Whether `evoke configuration apply` should restart the Conjur service.&lt;/P&gt;&lt;P&gt;3. Whether an additional command or manual service restart is required.&lt;/P&gt;&lt;P&gt;4. Whether this is a known defect with an available patch or fixed release.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2026 11:54:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/13-9-1-evoke-configuration-apply-does-not-activate/m-p/1425828#M2263</guid>
      <dc:creator>Jstechele</dc:creator>
      <dc:date>2026-10-06T11:54:25Z</dc:date>
    </item>
    <item>
      <title>Re: 13.9.1: evoke configuration apply does not activate authenticators defined in conjur.yml</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/13-9-1-evoke-configuration-apply-does-not-activate/m-p/1425829#M2264</link>
      <description>&lt;P&gt;Hi @Julien stechele​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you validate the conjur.yml permissions first? Similar to the ones mentioned in this thread&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/question/0D5Vy00003U0Mo4KAF/error-i-info-loading-conjur-config-file-etcconjurconfigconjurym&lt;/P&gt;</description>
      <pubDate>Fri, 09 Oct 2026 08:05:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/13-9-1-evoke-configuration-apply-does-not-activate/m-p/1425829#M2264</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-10-09T08:05:13Z</dc:date>
    </item>
    <item>
      <title>Re: 13.9.1: evoke configuration apply does not activate authenticators defined in conjur.yml</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/13-9-1-evoke-configuration-apply-does-not-activate/m-p/1425830#M2265</link>
      <description>&lt;P&gt; Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Indeed my permissions were wrong, thanks for pointing this out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also I've identified another bug: going from CONJUR_AUTHENTICATORS variable to enable/disable authenticators TO conjur.yml management and "evoke configuration apply" is not enough. I had to "sv restart conjur" before being able to manage authenticators via the conjur.yml file. It seems "evoke configuration apply" doesn't restart all the services it should restart.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2026 11:48:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/13-9-1-evoke-configuration-apply-does-not-activate/m-p/1425830#M2265</guid>
      <dc:creator>Jstechele</dc:creator>
      <dc:date>2026-10-12T11:48:43Z</dc:date>
    </item>
  </channel>
</rss>

