Has anyone faced errors 403 integrating Conjur with OpenShift using push-to-file mode?

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

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Has anyone faced errors 403 integrating Conjur with OpenShift using push-to-file mode?

L3 Networker

I have a Conjur integration with OpenShift. I first tried secret mode and it worked fine.

Now, I’m trying to use push-to-file mode with the same conjur host, ConfigMap, and ServiceAccount,

The authentication worked I got the message "Successfully authenticated".

but during the secret fetch I’m encountering the following error:

CSPFK019I Error fetching secrets, deleting secrets file

After a few attempts, I also got this log:

CSPFK038E Retransmission backoff exhausted %!(EXTRA *response.ConjurError=403 Forbidden)

403 Forbidden

 

I can see in the Conjur logs that authentication to the webservice was successful, but I don’t see any logs related to the secret fetch error.

4 REPLIES 4

L1 Bithead

@l b​ , Please check the audit logs as it seems like the host authenticates successfully but is having permissions issue when retrieving the secret.

I am using the same host that I used for secrets mode, worked there.

This is the log for the secrets mode

 

INFO: 2025/07/24 17:59:51.152996 conjur_secrets_retriever.go:101: CSPFK003I Retrieving following secrets from DAP/Conjur: [secret-name]

INFO: 2025/07/24 17:59:51.163926 provide_conjur_secrets.go:394: CSPFK020I No change in Kubernetes secret, no secrets updated

INFO: 2025/07/24 17:59:51.163943 provide_conjur_secrets.go:195: CSPFK009I DAP/Conjur Secrets updated in Kubernetes successfully.

 

@l b​ Please check the Conjur container(& audit) logs where the OpenShift is connecting to as these logs will have more information on what is the issue. OpenShift POD logs indicate an issue with the secret retrieval and the POD fails due to multiple failed retrievals.

L3 Networker

It was an access issue. I reproduced the error by removing the secret access for my host, and I got the same 403 error.

Later, I realized that the service account I was using belonged to a different host, so the host I was testing with didn’t have access to the secret I was trying to retrieve.

Thank you!

  • 211 Views
  • 4 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!