Secrets Management Articles
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Synchronizer's job is to push secrets from the Privileged Account Manager (PAM) Vault to the Conjur Vault. To perform its job, it stores some metadata concerning its last synchronization for each Line of Business (LOB) user. The next synchronization it run, it will compare this metadata with the metadata of the secrets to determine if the secrets need to be rotate.  Case 1 : - Last synchronization occurred 10min ago, secrets have been changed 3min ago -> The secret will be push into Conjur Case 2 : - Last synchronization occur 10min ago, secrets have been change 30min ago -> The secret should already be into Conjur and do not need to be push again.  This workflow is in place to optimize the way the synchronizer work.  However after restoring from a back up that can be a problem, and some secrets might be restore to previous version and will not be touch by the synchronizer before there next rotations.  This is one of the reason why you might want to force the resync of all the secrets in Conjur.  Steps To Force a full synchronization you need to perform the following : - Connect to the synchronizer server. - Stop the "Idira Vault-Conjur Synchronizer" service. - Move to that directory : C:\Windows\System32\config\systemprofile\AppData\Roaming\CyberArk\VaultConjurSynchronizer\metadata For versions below 13.0: C:\Windows\System32\config\systemprofile\AppData\Roaming\CyberArk\VaultConjurSynchronizer\ - Remove all the file named as follow : <LOBUser>.dat - Start the "Idira Vault-Conjur Synchronizer" service The <LOBUser>.dat contain the information of when the last synchronization occurs. By removing it, the synchronizer will consider it never synchronize the secrets of that LOBUser and will resynchronize all it secrets and create a new <LOBUser>.dat file.
View full article
For Conjur 13.0+ versions, there are four Postgresql settings that should be changed when increasing the supported Standby and Follower count from the default of 16 Steps These are: ===== - 'max_wal_senders': Default is 16. This should equal the maximum number of Standbys and Followers planned in the Conjur deployment. - `max_connections`: Default is 100. This should increase by 2 for each additional Follower planned about the default. For example, if the `max_wal_senders` is increased to 20, then `max_connections` should be at least 108. - `max_worker_processes`: Default is 26. This should be at least 10 more than the max_wal_senders value. For example, for 20 wal senders, the max worker processes should be at least 30. - `max_replication_slots`: Default is 21. This should be at least 5 more than the max_wal_senders value. For example, for 20 wal senders, the max replication slots should be at least 25 ===== ------------------------------------------------------------------------------------------------------------------------------------------------------------------ For versions prior to 13.0, there are only two parameters to configure per your needs: "max_connections" and "max_wal_senders" The process for managing them is here: Changing the "max_connections" and "max_wal_senders" for DAP containers
View full article
After removing accounts from a group, the Synchronizer did not sync them as two single accounts. There is still one virtual account in the Conjur. Is this expected behavior? How could we synchronize two individual accounts not in the Group? After removing accounts from the group, how do we get two accounts instead of one virtual account in the Conjur? How could we remove the empty group from the Vault? (deleting the last account from the group, the group would not be removed) Issue Please provide instructions on how to split accounts (Dual Accounts) within a group back into individual accounts Case: We removed the accounts from the group, but Synchronizer did not sync them as 2 single accounts. There is still one virtual account in the Conjur. The questions are the next: 1. Is this expected behaviour? 2. How could we synchronize 2 individual accounts not in the Group? 3. After removing accounts from the group, how do we get 2 accounts instead of 1 virtual account in the Conjur? 4. How could we remove the empty group from the Vault? (We thought that by deleting the last account from the group, the group would also be removed)   Environment Vault Conjur Synchronizer Documentation Resolution The rotational group setting is required for CPM to detect that accounts require a password change. This group however has absolutely no impact on Synchronizer - Synchronizer does not read it, doesn't know about its existence and does not indicate to Synchronizer that certain accounts are in dual account setup. Synchronizer recognizes dual accounts by the three attributes: - VirtualUserName - Index - DualAccountStatus.  The logic is the next: - if an account has these three attributes (ALL three attributes must be there), it's recognized as a dual account - if those three attributes are not set, it's treated as a single account. So, answering to those questions: 1) Yes, this is expected behaviour. Accounts with attributes VirtualUserName, Index and DualAccountStatus are synced with VirtualUsername as an identifier (no need to be in a group but must have status Active). 2) To sync two individual accounts - do not set VirtualUserName, Index and DualAccountStatus attributes on them. 3) Removing accounts from the group has no impact on Synchronizer. You must remove the VirtualUserName, Index and DualAccountStatus attributes to sync them as two separate accounts. 4) Delete it via PAClient, for example Steps The rotational group setting is required for CPM to detect that accounts require a password change. This group, however, has absolutely no impact on Synchronizer - Synchronizer does not read it, doesn't know about its existence, and does not indicate to Synchronizer that certain accounts are in dual account setup. Synchronizer recognizes dual accounts by the three attributes: - VirtualUserName - Index - DualAccountStatus.  The logic is the next: - if an account has these three attributes (ALL three attributes must be there), it's recognized as a dual account - if those three attributes are not set, it's treated as a single account. Answering to those initial mentioned questions: 1. Yes, this is expected behavior. Accounts with attributes VirtualUserName, Index, and DualAccountStatus are synced with VirtualUsername as an identifier (no need to be in a group, but must have status Active). 2. To sync two individual accounts - do not set VirtualUserName, Index, and DualAccountStatus attributes on them. 3. Removing accounts from the group does not impact Synchronizer. However, you must remove the VirtualUserName, Index, and DualAccountStatus attributes to sync them as two separate accounts. 4. Delete it via PAClient, for example.
View full article
Introduction This how-to guide describes how to apply patches, updates, and perform other routine maintenance on a DAP node in an auto-failover cluster without inadvertently triggering a failover. Background The DAP auto-failover feature detects when the active DAP Master becomes unresponsive and automatically promotes a DAP standby to take its place. However, the conditions caused by failure events (e.g. power outage, network loss, etc.) may also be caused by routine maintenance events that reboot nodes or cause the network to be temporarily unavailable. When these routine maintenance events trigger a failover, it requires additional effort to repair the DAP cluster and return it to a state that is resilient to true failures again. Alternative This guide provides a procedure for temporarily disabling auto-failover during maintenance periods. However, many customers have successfully deployed auto-failover clusters with a longer time-to-live (TTL) intended to withstand these short-lived outages. For example, a TTL of 5 minutes (300 seconds) is often sufficient to allow the nodes to reboot without falsely triggering a failover. See Modify Auto-Failover Cluster TTL  for more details on how to accomplish this.   Steps Procedure for Patching an Auto-failover DAP Cluster 1. Disable  cluster  Service on Standbys Disabling the  cluster  service on the Standbys prevents them from attempting to promote to Master while the active Master is temporarily down for maintenance. For each Standby in the auto-failover cluster: Connect to the Standby node (e.g. using SSH) Disable the  cluster  service with the following command in the DAP container: sv down cluster For example: $ docker exec dap sv down cluster It is not necessary to disable the  cluster  service on the active Master node. 2. Perform Node Maintenance Once the  cluster  service is disabled on all Standbys, each of the nodes in the Master cluster may be brought offline, rebooted, etc. without triggering a failover from the active Master to a Standby. 3. Verify Master is Healthy Once maintenance is complete, verify the Master is currently healthy according to its  /health  API endpoint: ... "cluster": { "ok": true, "status": "running", "message": "acting as master" }, "ok": true, "role": "master" 4. Re-enable the  cluster  Service on each Standby For each Standby in the auto-failover cluster: Connect to the Standby node (e.g. using SSH) Re-enable the  cluster  service with the following command in the DAP container: sv up cluster For example: $ docker exec dap sv up cluster 5. Verify Auto-failover Cluster is Healthy Once the  cluster  service is re-enabled on the Standbys, verify the cluster is healthy. Verify the Master is currently healthy according to its  /health  API endpoint: ... "cluster": { "ok": true, "status": "running", "message": "acting as master" }, "ok": true, "role": "master" Verify each Standby is healthy according to its  /health  API endpoint: ... "cluster": { "ok": true, "status": "standing_by", "message": null }, "ok": true, "role": "standby"
View full article
Question What are the various command options for execution under Evoke Command? Answer The various command options which can be run with Evoke command are as shown in the screenshot below :
View full article
For Conjur Follower deployed with conjur-appliance image, we can simply use any of the following methods to enable authenticator: 1. Use evoke command: evoke variable set CONJUR_AUTHENTICATORS authn-k8s/dev-cluster (assuming authenticator to be enabled is authn-k8s/dev-cluster)  2. Add the following line in /opt/conjur/etc/conjur.conf file in the Kubernetes Follower, followed by the restart of conjur, postgres, and nginx services. CONJUR_AUTHENTICATORS=authn-k8s/dev-cluster However, in the Conjur Follower Operator deployed with OpenShift OLM: - conjur.conf file is not present, and - evoke command is not available.   Steps For Conjur Follower deployed with conjur-appliance image, follow the steps below for enabling authenticator: (assuming authenticators to be enabled are both "authn" and "authn-k8s/dev-cluster") 1. Ensure that you have a local conjur.yml file with content as follow: #List of authenticators enabled for this node authenticators: - authn-k8s/dev-cluster - authn Reference: https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-DAP/12.6/en/Content/Deployment/DAP/manage-config-file.htm 2. Using oc command to apply local conjur.yml file above to the Kubernetes Follower by storing the file in a ConfigMap: oc create configmap -n cyberark-conjur conjur-config --from-file=conjur.yml=path/to/local/conjur.yml For reference, refer to this section: "4. (OPTIONAL) Create a ConfigMap for the Conjur configuration file" , under: https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-DAP/12.6/en/Content/Integrations/k8s-ocp/k8s-k8sfollower-dply.htm#configmap-config 3. During the deployment of Kubernetes Follower, ensure that under "From a ConfigMap", enter ConfigMap key and name created earlier: -Key: conjur.yml -Name: conjur-config For more details, refer to the "5. Deploy the Kubernetes Follower" step mentioned in: https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-DAP/12.6/en/Content/Integrations/k8s-ocp/k8s-k8sfollower-dply.htm#configmap-config ​​​​​​​
View full article
According to the documentation, so far Podman versions 3.3 and 3.4 are supported for deploying Leader, Standbys, and Followers: https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-DAP/latest/en/Content/Deployment/platforms/dap-sysreqs-server.htm#Supportedcontainerplatforms However, the default versions of Podman installed on RHEL 8.X is:   Steps In order to install the supported Podman version please run the next command:     dnf install podman-3.4.2 In case there is necessary first to remove the previously installed version (the default one), it could be done for example by executing the next:     yum remove module -y container-tools:3.0      yum module reset container-tools:rhel8 and then, proceed with 'dnf' command above ############# Some warning messages could be observed after the installation like:     WARN[0000] Failed to decode the keys ["network.network_backend"] from "/usr/share/containers/containers.conf".  These warnings are caused by an uncorrected configuration into the file linked there /usr/share/containers/containers.conf that contains an unsupported string (for Podman 3.X):     network_backend = 'cni' So, comment on that line or remove it, and the warnings should disappear  
View full article
Question How to verify if a Key is associated to a Certificate using OpenSSL? Answer To compare the Key and the Certificate, you should execute the following commands. The second command will require the private key password. Compare the output from both commands. If both md5 checksums match, the key and certificate go together. openssl x509 -modulus -noout -in conjur-authn-k8s-cjrpre-ca-cert.txt | openssl md5 c61944846fd055ddb94c21374d76c75b   openssl rsa -modulus -noout -in conjur-authn-k8s-cjrpre-ca-key.txt | openssl md5 Enter pass phrase for cs_privkey.txt: c61944846fd055ddb94c21374d76c75b where: conjur-authn-k8s-cjrpre-ca-cert.txt is the certificate. conjur-authn-k8s-cjrpre-ca-key.txt is the private key. In the previous example, as both command outputs are identical, the certificate and the key match. If you are unable to find the private key that corresponds to your certificate, you will need to replace the certificate.
View full article
Question What is expected in the Conjur.conf, Conjur.identity, and Secrets.yml files? Answer The files contain the following expected values: Conjur.conf:   --- account: <account> plugins: [] appliance_url: https://appliance.url.com netrc_path: "/etc/conjur.identity" cert_file: "/etc/<accountname>.pem" conjur.identity:   machine https://leader-vip.environment.com/authn login host/my_host password passwordforauthn secrets.yml:   AWS_ACCESS_KEY_ID: !var aws/iam/user/robot/access_key_id AWS_SECRET_ACCESS_KEY: !var aws/iam/user/robot/secret_access_key  
View full article
  • 79 Posts
  • 9 Subscriptions