Skip to content

Comments

Add TLS standardization for platform, mongo, gateway & redis roles#300

Open
Amunagala-itential wants to merge 11 commits intoitential:feature/v4from
Amunagala-itential:feature/v4-tls-changes
Open

Add TLS standardization for platform, mongo, gateway & redis roles#300
Amunagala-itential wants to merge 11 commits intoitential:feature/v4from
Amunagala-itential:feature/v4-tls-changes

Conversation

@Amunagala-itential
Copy link
Contributor

PKI Standardization and Hostname-Based Certificate Support

Summary

Standardized PKI implementation across MongoDB, Redis, Platform, and Gateway roles with hostname-based certificate naming to support multi-server deployments with unique certificates per host.

Problem

  • Hardcoded certificate names (server.pem, redis.crt) prevented multi-server deployments
  • Inconsistent PKI paths across roles (/etc/ssl/, /opt/itential/)
  • No flexible certificate strategy support (per-host, per-role, wildcard)

Solution

  • Hostname-based certificate naming using {{ inventory_hostname }}
  • Standardized PKI directory structure (/etc/pki/*)
  • Comprehensive PKI variables for all roles
  • Certificate preparation automation script
  • Support for 3 deployment scenarios via configuration

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are also some changes I anticipate to set the appropriate SE Linux labels on files. We can address that separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants