Benches macOS

11

Help with expiring Default certificate

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I need some help, I'm not sure how to go about reactivating or extending this certificate... I am getting this message:

+The following certificate is about to expire on your server, (servername):+

+ +

+ Name: Default+

+ Expiration Date: 2009-12-16 18:34:33 -0500+

My question is, do I delete this Default cert and make a new one called the same name, or...?

Thanks in advance.

Message was edited by: ekal

11 replies

Sign in or join Beachball Help to reply.

  1. 0

    Antonio Rocco

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi

    Edit it and extend it to a date you can live with. Does not have to be a year hence.

    Tony

  2. 0

    ekal

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi, thanks, I would love to but do not see how to edit.

    My options (as far as I see) are to delete it or create a new one.

    Where do I edit the certificate?

    Thanks.

  3. 0

    Antonio Rocco

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi

    Server Admin > Server Name > Certificates > Edit.

    Tony

  4. 0

    foilpan

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    if this is 10.6 server, the options look different. i'm not sure if there's an easy way to edit a self-signed cert in the server admin gui any more.

  5. 0

    Antonio Rocco

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi foilpan

    I did one last month and I could be wrong but it looked the same to me? I edited it post install to expire 3 years from the install date.

    Tony

  6. 0

    ekal

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    http://i47.tinypic.com/ekixoz.jpg

    There is a shot of the certs screen.

    The manual seems to indicate you can only replace a cert with a new certificate. What I can't figure out is how to get the keys to match? Having a tough time decoding what all of this is.

    The one selected in the image is the one I am trying to replace / update.

  7. 0

    Shane Depner1

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi,

    You can’t “edit” the existing cert anymore.

    You have to delete your expired (or soon to expire) cert if the new cert will be for the same host name, which is likely else you’ll get an error about it already existing in the chain. Just go to the certificate window, press the + and select “create a certificate identity”. Use the fully qualified domain name that matches the service or purpose of the cert and host. This will create a new self signed cert that is good for one year by default. If you want to create a cert with a different expiration date (more than 365 days), you must check the box to override defaults or something alone those lines when you’re creating the cert. That part is pretty self explanatory.

    I’m not sure if clients will have to “trust” the “new” self signed cert each time you do this. I don’t have time to test that as I was just looking at this during a meeting :P Not sure if you have to “repoint” your services to the new cert either but that’s fairly trivial even if you must do so. I assume you don’t have to though as long as the cert name remained the same and continues to match.

  8. 0

    ekal

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    The certificate is titled Default and as far as I can tell there is no specific 'fully qualified domain name'

    How do I find it, if there is one? I guess I'm unsure how to tell what services / purpose this cert is being used for / touched by?

  9. 0

    MrHoffman

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Nuke the default certificate? That's not (unless you have something referencing it) not necessary.

    If you want more options than what Server Admin offers here, go after the System Certificates using the Keychain Access tool (look in Applications / Utilities); you can import and export and other such there.

    If you want to establish blanket trust for your own stuff, you have to load the public root certificate for the CA; for yourself as a CA. This sequence is basically what purchasing a certificate does for you. A purchased certificate is tied to a root certificate that the certificate vendor has gotten registered in various browsers and tools.

    If you're working within your own organization and your own clients, it's usually just as effective and it's cheaper to set up your own root cert and your own trust. To be your own CA.

  10. 0

    ekal

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    OK so I decided to take a leap of faith and deleted the certificate.

    aaaaaand nothing has happened so far. It just might be the case that nothing was depending on it. I have a 2nd certificate which covers our local domain (intranet) which I can easily recreate when it expires in a year.

  11. 0

    Shane Depner1

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    In
    ALL of my 10.6 boxes, the default cert that has been created matches the FQDN and this is without any modification or changes. It doesn’t work anything like the interface did in 10.5 (in case anyone is referencing a 10.5 box for some reason).

    In any case, I found it easiest to do as I mentioned, which was to create a new cert with the appropriate name but with an expiration date that made sense. I then set my services to use this cert (so for host.com, i have a corresponding cert with the same name). This all works fine for me. Note that on the machines in production, I am using a godaddy cert as opposed to self signed.

    On
    NONE of my 10.6 boxes has a cert titled “default” been created on its own. The only reason I “removed” the original cert with the 1 year expiration is that I obviously could not create a second cert with the same exact host name because keychain would complain that one already exists in the chain.

    Anyway...works fine for me this way.