0
votes

I have a scenario that might have been asked before. I want to use WIF with a windows client but my STS would be behind a firewall and I need to augment the STS to deal with custom authentication. The call flow would be Client - calls authenticate on Security Service with custom RST claims token - Security Service - calls existing asmx service to validate user and retrives custom athentication values - Security Service - calls custom STS to create a Saml2 token and sends it back down to the client.

Once back on the client I have a secured token that I can use to call other WCF services that are WIF enabled.

Any examples on how this could work? Or did I miss n understanding somewhere in all my reading?

Thanks,

1
What are you using for your STS? I don't see anything too out-of-the-ordinary with what you're proposing.Garrett Vlieger

1 Answers

1
votes

The network requirements in this scenario are:

  1. The STS needs to be reachable by the client
  2. The WCF service needs to be reachable from the client
  3. The user validation ASMX service needs to be reachable by the STS

There are many examples of #1 and #2. It's all fairly standard. Look in the WIF SDK or the "Active" samples in the claims guide. Calling a custom ASMX to validate a user is well....custom. An implementation detail of your STS (which would have to be custom too, not an off-the-shelf STS like ADFS v2)