domain-restricted certificates [#537022]

Once #537020: create SSL certificate content type gets out the door, the frontend will then need to have a notion of "domains associated with the certificate". This will start blending in with DNS (although we don't necesssarily want to create zone files when we discover certificates!).

A given cert is always associated with a domain, and that is inscribed in the certificate itself. That can be parsed by the backend and sent to the frontend so that only the relevant certificates are shown to the user.

This is part of #394452: Full SSL support.

Comments

Comment #1

anarcat CreditAttribution: anarcat commented 31 July 2009 at 22:25

Project:

Hosting

» Hostmaster (Aegir)

this touches both frontend and backend

Comment #2

adrian CreditAttribution: adrian commented 14 July 2010 at 06:22

At the moment certificates are associated to clients only. And we need to introduce a top level domain/zone entity before we can tackle this.

i'd like it to be handled the same way as the certs are. IE: you dont have to go generate them seperately, it just happens during site creation.

Comment #3

adrian CreditAttribution: adrian commented 14 July 2010 at 06:23

oh, i forgot to say.

We store a 'ssl_key' now, which is just a textual identifier to the right path. This key defaults to the domain name you have entered on the form. * isn't an allowed character at the moment, but we could move it in that direction if we wanted to.