Re: format of service principal name (SPN)
- From: "Johnny" <prem14@xxxxxxx>
- Date: Wed, 26 Apr 2006 10:41:18 +0100
Thanks for the response. Yes this is in reference to Kerberos entities. The
SPN allows
us to use the syntax I mentioned but for some reason it does not work with
spaces in the servicename part (which accroding to docmumentation can be the
distinguished name or ldap name of the service). Delegation of impersonated
credentials to a remote server fails because the remote server receives the
"anonymous logon" credential.
Thanks for any help
Shakti
"Roger Abell [MVP]" <mvpNoSpam@xxxxxxx> wrote in message
news:%23anIGyNaGHA.3740@xxxxxxxxxxxxxxxxxxxxxxx
SPNs are Kerberos entities and they make use the the Kerberos
canonical name. The distinguished names you mention sound like
Ldap names.
"Johnny" <prem14@xxxxxxx> wrote in message
news:%23uSzc4GaGHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
We need to set up the service principal name for a service in this format
<class>/<host:port>/<service name>
we provide the distinguished name of the service in question. However we
found that this cannot have spaces in them. Surely distinguished names of
objects can have spaces in them. Can you suggest a solution to this. If
we use object guid what format do we enter that?
Thanks
Shakti
.
- Follow-Ups:
- Re: format of service principal name (SPN)
- From: Joe Richards [MVP]
- Re: format of service principal name (SPN)
- References:
- format of service principal name (SPN)
- From: Johnny
- Re: format of service principal name (SPN)
- From: Roger Abell [MVP]
- format of service principal name (SPN)
- Prev by Date: Re: Group Policy
- Next by Date: Re: Offline Root CA CDP Expiring
- Previous by thread: Re: format of service principal name (SPN)
- Next by thread: Re: format of service principal name (SPN)
- Index(es):
Relevant Pages
|