scep
community.hashi_vault
scep | community.hashi_vault | |
---|---|---|
2 | 15 | |
309 | 79 | |
1.0% | - | |
5.5 | 6.8 | |
12 days ago | about 2 months ago | |
Go | Python | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
scep
-
Easy HTTPS for your private networks
> You need a PKI which exposes a SCEP endpoint (ejbca or dogtag supports this).
Uhh...
> [...] ejbca [...]
Now you have two problems.
What I mean is, if you’ve been already running EJBCA for whatever reason then this is perhaps reasonable, but if your current setup is at the level of typing `openssl req` into a terminal (whether that’s a good idea or not), this sounds like a lot of additional complexity. (Can’t say anything about dogtag.)
I’ve been waiting forever for somebody to add an ACME backend to the Go SCEP library[1], but it doesn’t look like that happened. In the meantime it makes a fairly competent standalone server at the abovementioned invoke-openssl-by-hand level.
[1] https://github.com/micromdm/scep
-
Anyone using micromdm/scep server with SCEP profile?
The SCEP is working as it has no issue with our Macs and Jamf. Has anyone gotten this https://github.com/micromdm/scep to work with Intune? If so, would be nice to share the exact steps. CA has been added to root and the config to the scep is setup sort of following this https://www.ironwifi.com/help/scep Yet the scep profile fails when it gets pushed out. I just have under assignment status: "Error". The root certificate config profile pushes out successfully.
community.hashi_vault
-
Easy HTTPS for your private networks
My way of doing private SSL (not necessarily the easiest):
* own CA, to be distributed to all systems via Ansible playbook or Dockerfile directives
* Hashicorp Vault with enabled PKI engine
* Ansible Hashivault module [1]
* Ansible role & playbook to tie it all together
* CI enviroment for automated deployment of SSL certs to target systems
Works flawlessly once set up, including restart/reload of affected services. Might do a writeup on my personal blog at some point.
[1] https://github.com/ansible-collections/community.hashi_vault
-
The Bullhorn #102 (Ansible Newsletter)
community.hashi_vault 5.0.0 has been released. See the collection changelog for details.
-
The Bullhorn #100 (Ansible Newsletter)
community.hashi_vault version 4.2.1 has been released with updated documentation for the vault_kv2_write module. There are no functional changes.
-
The Bullhorn #97 (Ansible Newsletter)
community.hashi_vault version 4.2.0 [changelog] has been released with a new KVv2 write module and a warning/deprecation for duplicated term string option use in the hashi_vault lookup.
-
The Bullhorn #88 (Ansible Newsletter)
The community.hashi_vault collection has released version 4.1.0 with a new vault_list module and lookup from a new contributor! There are also some upcoming deprecation announcements for hvac and ansible-core support.
-
The Bullhorn #81 (Ansible Newsletter)
community.hashi_vault version 4.0.0 has been released, with previously announced breaking changes to some default values, and improvements to module documentation with attributes that describe the use of action groups and check mode support.
-
The Bullhorn #71 (Ansible Newsletter)
community.hashi_vault version 3.2.0 has been released with support for the azure auth method, thanks to new contributor @jchenship. This release also includes retries on HTTP 412 and a bugfix affecting requests>=2.28.0.
-
The Bullhorn #68 (Ansible Newsletter)
community.hashi_vault has released version 3.1.0, announcing a change to a default value that will take place in 4.0.0.
-
The Bullhorn #65 (Ansible Newsletter)
The community.hashi_vault collection is looking for feedback about support for end-of-life Python versions going forward. Join the discussion.
-
The Bullhorn #60 (Ansible Newsletter)
community.hashi_vault version 3.0.0 has been released, dropping support for Ansible 2.9 and ansible-base 2.10, as well as removing some deprecated features.
What are some alternatives?
lexicon - Manipulate DNS records on various DNS providers in a standardized way.
community.general - Ansible Community General Collection
minica - minica is a small, simple CA intended for use in situations where the CA operator also operates each host where a certificate will be used.
cert-manager - Automatically provision and manage TLS certificates in Kubernetes
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
bettertls - BetterTLS: A Name Constraints test suite for HTTPS clients.
community-docs - docs.ansible.com/community
vscode-ansible - vscode/vscodium extension for providing Ansible auto-completion and integrating quality assurance tools like ansible-lint, ansible syntax check, yamllint, molecule and ansible-test.
community.internal_test_tools - Internal only, not for end users
community - This repository is being archived. See https://github.com/ansible-community/presentations and https://github.com/ansible-community/meetings for the new locations
controller_configuration - A collection of roles to manage Ansible Controller and previously Ansible Tower