Chef cookbook that configures Conjur machine identity and SSH configuration.
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
attributes
files
libraries
recipes
spec
templates/default
test
.dockerignore
.gitignore
.kitchen.yml
.rubocop.yml
Berksfile
Berksfile.lock
CHANGELOG.md
Dockerfile.unit
Gemfile
Jenkinsfile
OFFLINE.md
PUBLISH.md
README.md
Rakefile
Vagrantfile
chefignore
jenkins.sh
kitchen.sh
knife.rb
metadata.rb
publish.sh
secrets.ci.yml
secrets.yml

README.md

conjur

Installs and/or configures Conjur, including Conjur SSH and command-line tools.

This cookbook is composed of several recipes, which can be used at different stages of the continuous delivery lifecycle.

The lifecycle is roughly intended to operate like this:

  • A base OS image from the CentOS or Ubuntu LTS family is selected.
  • The "foundation" cookbooks run on the base OS image to configure the connection to Conjur (and other desired systems), install packages, and perform static configuration.
  • A "foundation" image is captured after the foundation cookbooks have completed.
  • Machines are launched from the "foundation" image. Each machine is provided with Conjur identity, then a Chef run finishes the machine configuration (e.g. configure the host credentials for LDAPS connection to Conjur). At this point, Chef (or other configuration management tools) may also install and configure applications on top of the base OS foundation.

Foundation Recipes

These recipes can be used to build a "foundation" image, which is able to create a secure connection to Conjur, and has performed all package installation prior to the machine launch.

  • install [required] Installs base packages which are needed for Conjur SSH. All installation and configuration steps performed by this recipe can be built into an image.
  • conjurrc [optional] Configures the connection to the Conjur server endpoint and establishes SSL verification. This information can be safely built into an image.
  • client [optional] Installs the Conjur command-line tools. This is optional for Conjur SSH functionality. The CLI can be built into an image.

Launch recipes

  • configure Applies the Conjur host identity to finish the machine configuration.

Requirements

Platforms

  • Amazon Linux
  • CentOS 6
  • CentOS 7
  • Debian 8
  • RHEL 6
  • RHEL 7
  • Ubuntu 12.04 LTS
  • Ubuntu 14.04 LTS
  • Ubuntu 16.04 LTS

Dependency Cookbooks

  • sshd-service

Attributes

See attributes/default.rb for defaults and documentation.

Recipes

default

Runs the install and configure recipes.

install

Installs packages required for Conjur SSH. Packages install include:

  • openssh
  • PAM + LDAP
  • Conjur logshipper, which receives auth.log lines from syslog, parses them, and sends them to Conjur as login, logout, and sudo records.

This recipe also applies base configuration, such as:

  • Conjur update permission is mapped to a Unix user group
  • Conjur execute permission is mapped to a Unix user group
  • By default, the update Unix group is granted passwordless sudo access

client

Installs the Conjur command-line tools.

conjurrc

Creates the /etc/conjur.conf and /etc/conjur-[acct].pem from Chef attributes.

Tests

This cookbook is verified by both chefspec and serverspec tests. Conjur Inc also verifies the correct operation of the SSH functionality on all supported platforms.

Run jenkins.sh to lint and unit test.

Run jenkins_acceptance.sh to run EC2 integration tests. By default this script runs all test-kitchen suites defined in .kitchen.yml, but you can also pass a specific suite to run like so: jenkins_acceptance.sh ubuntu-16.

Offline installation

If the machines you'd like to conjurize with this cookbook are behind a firewall, please see OFFLINE.md for instructions.