Skip to content

Ansible Playbooks for deploying Conjur OSS for demonstration purposes

License

Notifications You must be signed in to change notification settings

infamousjoeg/deploy-conjur-oss

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

deploy-conjur-oss

Ansible Playbooks for deploying Conjur OSS for demonstration purposes

Table of Contents

Requirements

  • Python 3
  • pip
    • $ python3 -m ensurepip --upgrade
  • Ansible
  • Docker
    • $ curl -fsSL get.docker.com | sh
  • Docker SDK for Python
    • $ python3 -m pip install docker
  • community.general Ansible Collection
    • $ ansible-galaxy collection install community.general
  • cyberark.conjur Ansible Collection
    • $ ansible-galaxy collection install cyberark.conjur

Usage

Deploy

ansible-playbook site.yml

Deprovision

ansible-playbook deprovision.yml

Architecture Overview

nginx_proxy

Hostname: proxy

This is the proxy where all requests should be sent to. Listening on port 443, all requests will be proxied to conjur_server.

conjur_server

The Conjur appliance container. Accepts HTTPS requests routed through nginx_proxy at the hostname proxy.

postgres_database

The database backend for secret and ACL storage. All data is encrypted using the conjur_server CONJUR_DATA_KEY.

conjur_client

The CLI client container to communicate directly to conjur_server using.

The CLI will already be authenticated to conjur_server by the end of deployment tasks.

Username: admin Password: CYberark11!!

Access outside of container

$ docker exec conjur_client conjur authn whoami

Access from within container
$ docker exec -it conjur_client /bin/bash
root@cf497ec8fe6f:/# conjur authn whoami

About

Ansible Playbooks for deploying Conjur OSS for demonstration purposes

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published