Bug 250193
| Summary: | CS 7.2: CS.cfg contains internaldb.master.bindpwd as clean text | ||
|---|---|---|---|
| Product: | Red Hat Certificate System | Reporter: | Issue Tracker <tao> |
| Component: | CA | Assignee: | Bob Lord <blord> |
| Status: | CLOSED DUPLICATE | QA Contact: | Chandrasekar Kannan <ckannan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.2 | CC: | benl, tao |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-06-09 19:00:08 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 443788 | ||
|
Description
Issue Tracker
2007-07-30 22:40:24 UTC
After successful clone CA/TKS/DRM, the CS.cfg contains the internaldb master password.(see below) question: It is for preop parameters. It does NOT need after finish clone. Can I remove the preop.internaldb.master.bindpwd? preop.internaldb.master.basedn=o=CertificateServer preop.internaldb.master.binddn=cn=Directory Manager preop.internaldb.master.bindpwd=xxxxxxxxxxxx preop.internaldb.master.hostname=dsm-d01.hmca.ops.aol.com preop.internaldb.master.port=61391 preop.keysize.custom_size=2048 This event sent from IssueTracker by ble [SEG - Certificate System Engineering] issue 127437 Hi Kent, I believe that it should be safe to remove these lines (preop) in the CS.cfg after configuration successfully. Ben. Internal Status set to 'Waiting on Support' This event sent from IssueTracker by ble [SEG - Certificate System Engineering] issue 127437 User nkwan's account has been closed Bug already MODIFIED. setting target CS8.0 and marking screened+ *** This bug has been marked as a duplicate of bug 224726 *** |