I have a wcf application hosted in a windows service running a local windows account. Do I need to set an SPN for this account? If so, what's the protocol the SPN needs to be set under? I know how to do this for services over HTTP, but have never done it for net.tcp.
相关问题
- “Zero out” sensitive String data in Swift
- High cost encryption but less cost decryption
- How to make a .svc file write to asp.net Trace.axd
- WCF Service Using Client Certificates Requires Ano
- WCF error with net.tcp "The service endpoint faile
相关文章
- WCF发布Windows服务 POST方式报错 GET方式没有问题 应该怎么解决?
- Warning : HTML 1300 Navigation occured?
- XCopy or MOVE do not work when a WCF Service runs
- Security concerns about CORS
- How do I prevent SQL injection with ColdFusion
- Could not find default endpoint element that refer
- The 'DbProviderFactories' section can only
- Do I need to expose a constructor in a WCF DataCon
By default (i.e. out of the box) net.tcp services are unsecured and don't perform any authentication at all. So you won't need (and in fact can't) set a service principal name.
If you need to authenticate, then check the net.tcp security modes on MSDN. The best way to understand the different combinations is to experiment!
Change the service account to an AD account and register the SPN's as shown. Use your own service name e.g. fooservice
In the client config set: