Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace certificates in LDAP by Truststore configuration in default configuration #1733

Closed
gunterze opened this issue Dec 7, 2018 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@gunterze
Copy link
Member

gunterze commented Dec 7, 2018

Replace certificates in LDAP by Truststore configuration in default configuration for

  • standalone
dcmTrustStoreURL: ${jboss.server.config.url}/dcm4chee-arc/cacerts.jks
dcmTrustStoreType: JKS
dcmTrustStorePin: secret
dcmKeyStoreURL: ${jboss.server.config.url}/dcm4chee-arc/key.jks
dcmKeyStoreType: JKS
dcmKeyStorePin: secret
dcmKeyPin: secret
  • and docker installation
dcmTrustStoreURL: file://${env.TRUSTSTORE}
dcmTrustStoreType: JKS
dcmTrustStorePin: ${env.TRUSTSTORE_PASSWORD}
dcmKeyStoreURL: file://${env.KEYSTORE}
dcmKeyStoreType: ${env.KEYSTORE_TYPE}
dcmKeyStorePin: ${env.KEYSTORE_PASSWORD}
dcmKeyPin: ${env.KEY_PASSWORD}

so it becomes sufficient to modify the Keystore/Truststore file and/or environment variables to update used keys/certificates, without the need to modify also the LDAP configuration.

Requires dcm4che/dcm4che#381

@gunterze gunterze added the enhancement New feature or request label Dec 7, 2018
@gunterze gunterze added this to the 5.15.1 milestone Dec 7, 2018
gunterze added a commit to dcm4che-dockerfiles/slapd-dcm4chee that referenced this issue Dec 10, 2018
gunterze added a commit to dcm4che-dockerfiles/slapd-dcm4chee that referenced this issue Dec 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants