13.9.1: evoke configuration apply does not activate authenticators defined in conjur.yml

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

13.9.1: evoke configuration apply does not activate authenticators defined in conjur.yml

L0 Member

We are migrating authenticator configuration from the deprecated `CONJUR_AUTHENTICATORS` variable to `/etc/conjur/config/conjur.yml`.

 

The YAML is loaded correctly:

 

evoke configuration show

 

reports all authenticators with:

 

authenticators: value: - authn - authn-jwt/... - authn-k8s/... source: yml

 

 

However, after running:

 

evoke variable unset CONJUR_AUTHENTICATORS evoke configuration apply

 

 

the local `/info` endpoint reports only:

 

{ "authenticators": { "enabled": ["authn"] } }

 

 

Modifying the authenticator list in `conjur.yml` and applying it again does not change the enabled authenticators.

 

`evoke configuration apply` outputs:

 

Conjur server reboot initiated. New configuration will be applied.   ...   Config reload successful Syslog-ng service restarted.

 

 

However, unlike `evoke variable set`, it does not show the Conjur, seed, PostgreSQL, or nginx services being stopped and started.

 

Setting the deprecated variable works immediately:

 

evoke variable set CONJUR_AUTHENTICATORS "<comma-separated-list>"

 

 

This performs a full service restart, after which `/info.authenticators.enabled` contains the complete list.

 

We also observed that:

 

evoke variable unset --no-restart CONJUR_AUTHENTICATORS evoke configuration apply

 

 

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.

 

**Expected behavior**

 

`evoke configuration apply` should restart or reload all required services so that `authenticators` from `conjur.yml` becomes the effective runtime configuration.

 

Please confirm:

 

1. Whether YAML-managed authenticators are supported in this appliance version.

2. Whether `evoke configuration apply` should restart the Conjur service.

3. Whether an additional command or manual service restart is required.

4. Whether this is a known defect with an available patch or fixed release.

 

Kind Regards,

2 REPLIES 2

L4 Transporter

Hi @Julien stechele​ 

 

Can you validate the conjur.yml permissions first? Similar to the ones mentioned in this thread

https://community.cyberark.com/s/question/0D5Vy00003U0Mo4KAF/error-i-info-loading-conjur-config-file-etcconjurconfigconjurym

L0 Member

Hello,

 

Indeed my permissions were wrong, thanks for pointing this out.

 

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.

  • 34 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!