Simplest way to secure Azure Web Role WCF service -

Using the latest VS 2013 and Ezur SDK 2.4, I have created a web roll and WCF service in it. This service will be consumed by standard-generated .NET service reference client proxy.

I am trying to understand what is the simplest method to secure this WCF service. I mean it is an easy way to get certification, like clear text PWD etc. .

Some additional information about the use case:

• Only one user will
• The client app will be run in a safe location because the customer side Anyone in the secret (such as a user name / PWD or certificate) is perfectly fine to store
• I just want to stop my service only to be used by the public to run in my safe place Client app this Can access, I do not want anymore low.

That's why I'm goggling the web, I read more, and I'm confused and overwhelmed with the choices I have no scope for what I do not need. When searching for client certificates, I get more consolidated federal method methods with server-side temp shirts, etc., which I'm not sure is my easy-to-use case is necessary.

Any help appreciated in advance thanks

If you actually restrict access I would like to see client certificates. To configure blue for client certificates, a SO SO post seems to be very complicated, so I will refer you to this blog post and briefly write down [I recently used it myself, therefore I know that this works]

In short, you can create your own certificate using merchant [NOTE: You can create an official SSL certificate for your site And you can use self-signed only for your client certificates.]

You then configure your site to accept client seriet - I usually appcmd.exe and use a startup function, but as the blog post tells you that your site is not ready, you have to add it to your weblog OnStart method [I actually have Appcmd.exe start the path Went away and was very confused).

 using  (var serverManager = new ServerManager ()) {Try {var siteName = RoleEnvironment.CurrentRoleInstance.Id + "_Web"; Var config = serverManager.GetApplicationHostConfiguration (); Var accessSection = config.GetSection ("system.webServer / security / access", siteName); AccessSection ["sslFlags"] = @ "SSLNotAttert"; ServerManager.CommitChanges (); } Caught (Exception Pre) {...}}  

in the Certificate by Handler You can certify the certificate and if you want (and I suggest) that The client certificate is being sent by your expected CA (if signed by yourself) or the thumb impression of the certificate is that which you expect (if only one is going to happen) or the above combination.