|
|
You're in the
iis security
group:Windows 2003 R2 and WSE 3.0 Kerberos issue
iis security:
machine will be used as a stand alone demo machine) Working the Kerberos sample in %Program Files%Microsoft WSE\v3.0\Samples\CS\QuickStart\Security\WSSecurityKerberos\Policy It works fine with the service hosted by IIS in the Default App Pool. After changing it to a new App Pool under a different service account (member of Domain User, IIS_WPG, "Log on as service" right) I can call any endpoint not protected by the kerberos policy, but once calling the 'StockQuoteRequest' which requires a Kerberos token, I get this error at the server side: WSE594: AcceptSecurityContext call failed with the following error message: Logon failure: unknown user name or bad password. Appearently this service account does not have the rights to verify the Kerberos token? Some policy setting that I am missing? NOTE: As I said the R2 server is also a domain controller. This most likely complicates the issue, but still - Network Service works, so surely I can configure my service acocunt to work as well? Any ideas here? Thanks,
Well, just tried on a regular Windows 2003 SP1 - same issue and this one is
not a domain controller. So, I suppose I'm down to some right that needs to be set. Here is the full exception dump from my WSE trace: <soap:Fault> <faultcode xmlns:q0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">q0:InvalidSecurityToken</faultcode> <faultstring>Microsoft.Web.Services3.Security.SecurityFault: An invalid security token was provided ---> System.Security.SecurityException: WSE594: AcceptSecurityContext call failed with the following error message: Logon failure: unknown user name or bad password. .. at Microsoft.Web.Services3.Security.Tokens.Kerberos.KerberosServerContext.AcceptContext(Byte[] inToken) at Microsoft.Web.Services3.Security.Tokens.KerberosToken.InitializeServerContext() at Microsoft.Web.Services3.Security.Tokens.KerberosToken.InitializeLifeTime() at Microsoft.Web.Services3.Security.Tokens.KerberosToken.get_IsCurrent() at Microsoft.Web.Services3.Security.Security.LoadToken(XmlElement element, SecurityConfiguration configuration, Int32& tokenCount) The Zone of the assembly that failed was: MyComputer --- End of inner exception stack trace --- at Microsoft.Web.Services3.Security.Security.LoadToken(XmlElement element, SecurityConfiguration configuration, Int32& tokenCount) at Microsoft.Web.Services3.Security.Security.LoadXml(XmlElement element) at Microsoft.Web.Services3.Security.Security.CreateFrom(SoapEnvelope envelope, String localActor, String serviceActor) at Microsoft.Web.Services3.Security.ReceiveSecurityFilter.ProcessMessage(SoapEnvelope envelope) at Microsoft.Web.Services3.Pipeline.ProcessInputMessage(SoapEnvelope envelope) at Microsoft.Web.Services3.WseProtocol.FilterRequest(SoapEnvelope requestEnvelope) at Microsoft.Web.Services3.WseProtocol.RouteRequest(SoapServerMessage message) at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</faultstring> <faultactor>http://localhost/WSSecurityKerberosPolicy/WSSecurityKerberosService.asmx</faultactor> </soap:Fault>
Well, as it often goes, time - and your own effort - is on your side. The
issue is caused by missing Service Principal Names on my service account. It must be set to the same SPN as the computer account which is the account behind the Default App Pool (Network Service). So it had nothing to do with the fact that the server runs R2 or is a domain controller. Read here to get the full story: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/WSS_Ch7_KerbTechSupp.asp Niels [quoted text, click to view] "Niels Flensted-Jensen" wrote:
> Running a Windows 2003 R2 Standard configured as a domain controller (the > machine will be used as a stand alone demo machine) > > Working the Kerberos sample in %Program Files%Microsoft > WSE\v3.0\Samples\CS\QuickStart\Security\WSSecurityKerberos\Policy > > It works fine with the service hosted by IIS in the Default App Pool. > > After changing it to a new App Pool under a different service account > (member of Domain User, IIS_WPG, "Log on as service" right) I can call any > endpoint not protected by the kerberos policy, but once calling the > 'StockQuoteRequest' which requires a Kerberos token, I get this error at the > server side: > > WSE594: AcceptSecurityContext call failed with the following error message: > Logon failure: unknown user name or bad password. > > Appearently this service account does not have the rights to verify the > Kerberos token? Some policy setting that I am missing? > > NOTE: As I said the R2 server is also a domain controller. This most likely > complicates the issue, but still - Network Service works, so surely I can > configure my service acocunt to work as well? > > Any ideas here? > > Thanks, >
Hi,
I have the same problem with SPN. Although I set the SPN the same computer account "http/localhost:4115", the error still appear: "WSE594:InitializeSecurityContext call failed with the following error message: A specified logon session does not exist. It may already have been terminated." Do you have any experience on this error message? Hung. [quoted text, click to view] "Niels Flensted-Jensen" wrote:
> Well, as it often goes, time - and your own effort - is on your side. The > issue is caused by missing Service Principal Names on my service account. It > must be set to the same SPN as the computer account which is the account > behind the Default App Pool (Network Service). > > So it had nothing to do with the fact that the server runs R2 or is a domain > controller. > > Read here to get the full story: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/WSS_Ch7_KerbTechSupp.asp > > Niels > > > "Niels Flensted-Jensen" wrote: > > > Running a Windows 2003 R2 Standard configured as a domain controller (the > > machine will be used as a stand alone demo machine) > > > > Working the Kerberos sample in %Program Files%Microsoft > > WSE\v3.0\Samples\CS\QuickStart\Security\WSSecurityKerberos\Policy > > > > It works fine with the service hosted by IIS in the Default App Pool. > > > > After changing it to a new App Pool under a different service account > > (member of Domain User, IIS_WPG, "Log on as service" right) I can call any > > endpoint not protected by the kerberos policy, but once calling the > > 'StockQuoteRequest' which requires a Kerberos token, I get this error at the > > server side: > > > > WSE594: AcceptSecurityContext call failed with the following error message: > > Logon failure: unknown user name or bad password. > > > > Appearently this service account does not have the rights to verify the > > Kerberos token? Some policy setting that I am missing? > > > > NOTE: As I said the R2 server is also a domain controller. This most likely > > complicates the issue, but still - Network Service works, so surely I can > > configure my service acocunt to work as well? > > > > Any ideas here? > > > > Thanks, > >
Hung,
Have a look in the "Common Error Messages" in the "Troubleshooting WSE Applications" section in the WSE 3.0 documentation. Notice though that your SPN seems to be wrong. You need to set it as described by link I provided ( http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/WSS_Ch7_KerbTechSupp.asp). Note that you need to set two SPNs - with and without the domain name. And to do that you need to install the Windows Support Tools as mentioned in the article. Niels [quoted text, click to view] "Hung Ngo" wrote:
> Hi, > I have the same problem with SPN. Although I set the SPN the same computer > account "http/localhost:4115", the error still appear: > "WSE594:InitializeSecurityContext call failed with the following error > message: A specified logon session does not exist. It may already have been > terminated." > Do you have any experience on this error message? > Hung. > > "Niels Flensted-Jensen" wrote: > > > Well, as it often goes, time - and your own effort - is on your side. The > > issue is caused by missing Service Principal Names on my service account. It > > must be set to the same SPN as the computer account which is the account > > behind the Default App Pool (Network Service). > > > > So it had nothing to do with the fact that the server runs R2 or is a domain > > controller. > > > > Read here to get the full story: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/WSS_Ch7_KerbTechSupp.asp > > > > Niels > > > > > > "Niels Flensted-Jensen" wrote: > > > > > Running a Windows 2003 R2 Standard configured as a domain controller (the > > > machine will be used as a stand alone demo machine) > > > > > > Working the Kerberos sample in %Program Files%Microsoft > > > WSE\v3.0\Samples\CS\QuickStart\Security\WSSecurityKerberos\Policy > > > > > > It works fine with the service hosted by IIS in the Default App Pool. > > > > > > After changing it to a new App Pool under a different service account > > > (member of Domain User, IIS_WPG, "Log on as service" right) I can call any > > > endpoint not protected by the kerberos policy, but once calling the > > > 'StockQuoteRequest' which requires a Kerberos token, I get this error at the > > > server side: > > > > > > WSE594: AcceptSecurityContext call failed with the following error message: > > > Logon failure: unknown user name or bad password. > > > > > > Appearently this service account does not have the rights to verify the > > > Kerberos token? Some policy setting that I am missing? > > > > > > NOTE: As I said the R2 server is also a domain controller. This most likely > > > complicates the issue, but still - Network Service works, so surely I can > > > configure my service acocunt to work as well? > > > > > > Any ideas here? > > > > > > Thanks, > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |