Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Verified Answer
  • Replies replies
    7
  • Subscribers subscribers
    23
  • Views views
    712
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Certificate generating with old server name

benjaminhare

OES 2015.1 server was renamed.  The correct name is reflected in local hostname file, as well as nds.conf. Also, the server shows up under the correct name in eDirectory.  When the old certs expired and I regenerated new ones (ndsconfig upgrade) they were created with the old hostname.  Any ideas where/why ndsconfig is getting the old hostname?

  • 0  

    It would be interesting to compare with those created by the iManager, NetIQ Certificate Server, Repair Default Certificates.

    How is the general eDir health?   Do the following commands come back error free?

    ndsrepair -T
    ndsrepair -E
    ndsrepair -C -Ad -A

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0 in reply to   

    All of the above ndsrepair options complete with zero errors.  Also, I note the name of the server is correct in the ndsrepair output.  Thanks for the suggestion about using iManager.  I gave it a try and it still generates the the cert with the old name.  Your suggestions got me thinking about DNS resolution so I did a lookup and confirmed the forward/reverse DNS entries reflect the correct name.  We don't even have an alias record for the old name, so DNS is ruled out.

  • 0 in reply to 

    How do you renamed the server?
    Imho the only supported way is to remove the server from the tree with ndsconfig rm and rename the server (with yast) and readd the server with yast (or ndsconfig)

  • 0   in reply to 

    Check and edit if needed, the files
    /etc/hosts
    /etc/HOSTNAME

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0 in reply to 

    Opened a ticket with Micro Focus support and they had me change it in two places: nds.conf, and Yast -> Network Settings -> Hostname/DNS.  Restarted ndsd.  Name change was reflected in eDir and all seemed well until we had to gen new certs.

  • 0 in reply to   

    Confirmed both are correct.

  • Verified Answer

    +1

    Circling back on this issue.  I never found the root cause.  Over the Thanksgiving holiday I upgraded the server to OES 2018 SP3 and the problem mysteriously went away.  After the upgrade I deleted, then re-generated a new certificate and it was minted with the correct hostname.  So my issue has been resolved by the upgrade.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.