rbac

pdk
Exposes Puppet Enterprise Console RBAC APIs to the Puppet DSL

Puppet Training

pltraining

83,561 downloads

3,240 latest version

3.1 quality score

Version information

  • 0.0.10 (latest)
  • 0.0.9
  • 0.0.8
  • 0.0.7
  • 0.0.6
  • 0.0.5
  • 0.0.4
  • 0.0.3
  • 0.0.2
  • 0.0.1
released Apr 9th 2020
This version is compatible with:
  • Puppet Enterprise 3.7.x
  • Puppet 3.x
  • CentOS
    ,
    OracleLinux
    ,
    RedHat
    ,
    Scientific
    ,
    Debian
    ,
    Ubuntu
    ,
    windows

Start using this module

Documentation

pltraining/rbac — version 0.0.10 Apr 9th 2020

PE Console RBAC APIs

Puppet Enterprise 3.7 introduced a new Role Based Access Control layer. This enables you to manage the permissions of local users as well as those who are created remotely, on a directory service in very granular detail.

This module exposes some of it to the Puppet DSL. Currently, it manages users, roles, permissions, and groups.

Usage

rbac_user { 'testing account':
  ensure       => present,
  name         => 'testing',
  display_name => 'Just a testing account',
  email        => 'testing@puppetlabs.com',
  password     => 'puppetlabs',
  roles        => [ 1,2 ],
}

rbac_role { 'Viewers':
  ensure      => 'present',
  description => 'Viewers',
  permissions => [
  {
    'object_type' => 'nodes',
    'action' => 'view_data',
    'instance' => '*'
  },
  {
    'object_type' => 'console_page',
    'action' => 'view',
    'instance' => '*'
  }],
}

rbac_group { 'admins':
  ensure => 'present',
  roles  => ['Administrators'],
}

Limitations

The API does not currently allow you to update existing users, other than to revoke the account, or update the roles attached to the user. When you ensure an rbac_user is absent, the record will not be removed, just marked as revoked.

For a node that is not a standalone master to manage RBAC users, its certname must be listed in the Console node's RBAC certificate whitelist.

Contact

education@puppetlabs.com