|
Posted by JSC on February 15, 2008, 8:18 am
Please log in for more thread options Gotcha. Thanks.
"Brian Komar" wrote:
> I mean duplicating the Workstation Authentication certificate and changing
> the subject tab to state that the subject is provided in the request. You
> can then set permissions for a group that contains users who are local
> Administrators on the target boxes.
> Brian
>
> > Brian, thanks, that helped a lot in explaining things.
> >
> > Woud you mind expanding on the last part about creating a custom
> > certificate
> > template.
> >
> > Would this be like creating a template with a combination of workstation
> > and
> > user certificate? We are already using user certificates, would
> > workstation
> > and user signature only work?
> >
> > "Brian Komar" wrote:
> >
> >> Inline...
> >> > We are looking to deploy machine certs in our domain for 802.1x port
> >> > based
> >> > authentication.
> >> >
> >> > My question is what is the difference between the computer cert
> >> > template
> >> > and
> >> > the workstation cert template? Both say they can be used for
> >> > workstation/server authentication. Is the Computer cert a V1 cert and
> >> > the
> >> > Workstation V2? Anybody have any experience setting this up in their
> >> > environment that will be willing to share information, I would
> >> > appreciate
> >> > it.
> >>
> >> They are essentially the same. Both allow autoenrollment but through
> >> different mechanisms. Computer (a v1 cert) allows autoenrollment through
> >> ACRS. Workstation Authentication deploys through Autoenrollment Settings.
> >> >
> >> > In testing I have both workstation and the computer cert template
> >> > loaded
> >> > on
> >> > my CA, but I cannot seem to get these certs to show up as available to
> >> > request through the certificate web pages. I will need to be able to
> >> > do
> >> > this
> >> > for machines that are not connected to the domain to get it through
> >> > autoenrollment and Apple OS X machines.
> >>
> >> Neither is available through the Web pages because Web page requests are
> >> done in the security context of the user, and these certificates are
> >> requested through the machine's identity. You would have to create a
> >> custom
> >> certificate template (based on either workstation or computer) that
> >> allows
> >> the subject to be provided in the request.
> >>
> >> >
> >>
>
|