- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
05-29-2026 08:52 AM
Hey everyone, ran into this error recently and wanted to share the fix with the community. I also submitted an enhancement request here: https://community.cyberark.com/s/article/Conjur-Selfhosted-403-configurefollower-ERROR-Coul-bb20-439
[Conjur Self-hosted] Follower CrashLoopBackOff – seed generation 403 after configurator image update
Environment
Symptom
Follower stuck in
Init:CrashLoopBackOff
Log from the configurator
[configure-follower] INFO: Fetching seed file from https://<leader>/configuration/<account>/seed/follower
curl: (22) The requested URL returned error: 403
[configure-follower] ERROR: Could not download seed file from Leader: Insufficient permission to generate plaintext follower seed.
Audit log on the Leader (/opt/cyberark/conjur/logs/audit.log):
failed to check if can execute <account>:webservice:conjur/seed-generation/follower/plaintext :
Webservice 'conjur/seed-generation/follower/plaintext' not found in account '<account>'
Root Cause
The official documentation at docs.cyberark.com (version 13.8) still references the webservice name as
conjur/seed-generation
https://docs.cyberark.com/secrets-manager-sh/13.8/en/content/deployment/cnj-seedservice.htm
However, the conjur-openshift-follower-configurator image now checks permissions against a new path:
conjur/seed-generation/follower/plaintext
Solution
Create the new webservice and grant permission to the follower host. On the Leader:
yaml
---
# =================================================
# == Register the seed generation service
# =================================================
- !policy
id: conjur/seed-generation/follower/plaintext
body:
# This webservice represents the Seed service API
- !webservice
# Hosts that can generate seeds become members of the
# `consumers` group.
- !group consumers
# Authorize `consumers` to request seeds
- !permit
role: !group consumers
privilege: [ "execute" ]
resource: !webserviceconjur policy load -b conjur/seed-generation -f seed-follower-plaintext.yml
Then restart the follower:
oc rollout restart deployment/conjur-follower -n <namespace>
Outcome
Follower initializes successfully after the webservice is created.
Notes
This appears to be either a bug in the configurator image (calling the wrong path) or outdated documentation. I recommend CyberArk:
Hope this helps someone hitting the same issue!
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!

