Skip to content

laczau/ansible-authentication-services

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

One Identity open source projects are supported through One Identity GitHub issues and the One Identity Community. This includes all scripts, plugins, SDKs, modules, code snippets or other solutions. For assistance with any One Identity GitHub project, please raise a new Issue on the One Identity GitHub project page. You may also visit the One Identity Community to ask questions. Requests for assistance made through official One Identity Support will be referred back to GitHub and the One Identity Community forums where those requests can benefit all users.

Safeguard Authentication Services Ansible Collection

The One Identity Safeguard Authentication Services Ansible Collection, referred to as ansible-authentication-services, consists of roles, modules, plugins, report templates, and sample playbooks to automate software deployment, configuration, Active Directory joining, profiling, and report generation for Safeguard Authentication Services.

Collection Contents

Implemented

In Development

Future

Installation

Prerequisites

  • Ansible version 2.9 or later

    • Collections are a new feature introduced in Ansible version 2.9. Please use the latest 2.9+ release for the best user experience.
  • One Identity Safeguard Authentication Services version 4.2.x or later

From Ansible Galaxy

To install from Ansible Galaxy you can use the ansible-galaxy command to install the collection on your control node. See Ansible documentation for futher information.

Using ansible-galaxy command:

ansible-galaxy collection install oneidentity.authentication_services

The collection can also be added to a project's requirements.yml file

---
collections:
  - name: oneidentity.authentication_services

and installed using the ansible-galaxy command. This method allows all required collections for a project to be specified in one place and installed with one command.

ansible-galaxy collection install -r requirements.yml

When used with Ansible Tower and Ansible AWX the collections in the project's requirements.yml file are automatically installed each time a project is run and there is no need to use the ansible-galaxy command.

From GitHub

For the examples in this section please see ansible-authentication-services releases page to find the latest collection build artifact (*.tar.gz file) and use the URL to this file in place of the URL's shown below. The collection build artifact is under the 'Assets' section for each release (right click on the *.tar.gz file and select 'Copy link address' to copy URL).

To install from GitHub you can use the ansible-galaxy command to install the collection on your control node. See Ansible documentation for futher information.

Using ansible-galaxy command:

ansible-galaxy collection install https://github.com/OneIdentity/ansible-authentication-services/releases/download/v0.0.6/oneidentity-authentication_services-0.0.6.tar.gz

The collection can also be added to a project's requirements.yml file

---
collections:
  - name: https://github.com/OneIdentity/ansible-authentication-services/releases/download/v0.0.6/oneidentity-authentication_services-0.0.6.tar.gz

and installed using the ansible-galaxy command. This method allows all required collections for a project to be specified in one place and installed with one command.

ansible-galaxy collection install -r requirements.yml

When used with Ansible Tower and Ansible AWX the collections in the project's requirements.yml file are automatically installed each time a project is run and there is no need to use the ansible-galaxy command.

Local Build and Install

For local build and installation, you can clone the Git repository, build the collection artifact, and install the locally built collection artifact. This would be useful for those wishing to extend or customize the collection.

  1. Clone the Git repository:

    git clone https://github.com/OneIdentity/ansible-authentication-services.git
  2. Run a local build inside the collection using the ansible-galaxy command in the root directory of the cloned repository:

    cd ansible-authentication-services
    ansible-galaxy collection build

    The build command will generate an Ansible Galaxy collection artifact with a tar.gz file extension, sample output will look like the following:

    Created collection for oneidentity.authentication_services at /home/user/ansible-authentication-services/oneidentity-authentication_services-0.0.6.tar.gz
    

    Pleae note the path shown above is just an example, the path to your build artifact will be in the root directory of the cloned repository.

  3. Install the locally-built collection artifact using the ansible-galaxy command to install the collection on your control node. See Ansible documentation for futher information.

    Using ansible-galaxy command:

    ansible-galaxy collection install /home/user/ansible-authentication-services/oneidentity-authentication_services-0.0.6.tar.gz

    The collection can also be added to a project's requirements.yml file

    ---
    collections:
    - name: /home/user/ansible-authentication-services/oneidentity-authentication_services-0.0.6.tar.gz

    and installed using the ansible-galaxy command. This method allows all required collections for a project to be specified in one place and installed with one command.

    ansible-galaxy collection install -r requirements.yml

When used with Ansible Tower and Ansible AWX the collections in the project's requirements.yml file are automatically installed each time a project is run and there is no need to use the ansible-galaxy command.

Usage

The collection provides various sample playbooks in the examples directory.

Supported Platforms

All Safeguard Authentication Services supported platforms.

Notes

Known issues

  • Check mode does not work as expected for the client_sw role. No changes are made and it doesn't cause errors but the stated changes that would or would not be made if run normally are not accurate.
  • The directory of client software install packages has to be on the Ansible control node. It would be nice to be able to point to this directory on another machine but this is not possible at this time.
  • The IPV4 address for HP-UX machines does not show up in the CSV and HTML reports, this is due to differences in how facts are reported for this OS. No plan to fix this issue at this time.

TODO's

  • Implement client_profile role.
  • Other roles/features depending on interest may include roles to automate server software deployment, server configuration, and server profiling.

About

Ansible automation for Authentication Services

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Python 51.6%
  • HTML 48.4%