Sorry about the long unexplained absence. I hated starting this topic and then not being able post for a couple of weeks. But I'm back and ready to continue configuring stuff. Stuff like a server. This post is pretty easy since it is so similar to my last post on configuring the client. In fact, I reused several of the images from that post.
To start, get into the WSE Settings 3.0 editor. Unlike the client application, you'll have to check the "Enable the Microsoft Web Services Enhancement SOAP Protocol Factory" checkbox (Figure 1) to add a reference to the "Microsoft.Web.Services3" assembly. Click the "Policy" tab to begin adding your new policy (Figure 2).
| 
|
| Figure 1 | Figure 2 |
Go ahead and add a policy. The first two screens, the Welcome (Figure 3) and Authentication Settings (Figure 4) screens, should be pretty familiar. On the Authentication Setting screen make sure you are securing a service application and the client authentication method is "Username".
| 
|
| Figure 3 | Figure 4 |
If we were interested in authorizing access to our web services through Active Directory, we would be making some changes to the "Users and Roles" (Figure 5) screen. Since we want custom authorization, we want to leave the "Perform Authorization" checkbox unchecked. Click "Next" to go to the "Message Protection" (Figure 6) screen. Make sure that whatever settings selected for the client are also selected for the service. In our case, we want to Enable WS-Security 1.1 Extensions and set the Protection Order to "None".
|  |
| Figure 5 | Figure 6 |
The last screen you will get is the Summary screen (Figure 7). You're done with the wizard and almost done with configuring the service. All that is required now is to configure a reference to the token manager you will be using (more on this in my next post). Click the Security tab to add a Security Token Manager (not a
Binary Security Token Manager). The screen should look something like Figure 8.
| 
|
| Figure 7 | Figure 8 |
Click the "Add" button under "Security Token Manager" to get the Security Token Manager Screen in Figure 9. There are several Managers that we could choose from, but we are only interested in the "Username Token Manager" for now. Select it and click OK. Close the main configuration screen and you have configured your service.
 | |
| Figure 8 | |
In my next post, I'll create a TokenManager object that will be able connect to the dataset I showed in the second post of this series.
