Identity

Security in the Cloud

I was impressed with my first taste of ADFS on my last project. Specifically solving for Web SSO. Geneva, (aka Zermatt) is now the single federated identity platform. And it sits in the Cloud. At the PDC 1 Day (MSDN Dev Con) the presentation on Azure noted this. This is wonderful. It may be new to us at this point, but it will be the same framework in the enterprise as in the cloud. A Security Token Service (STS) will exist in the cloud, a portal to manage the access control rules will exist in the...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Development under claims based identity

We implemented Web SSO with ADFS. It works great, but the development experience was limited to W2K3. This was a problem as development workstations were XP. So we had 1 server on the side to test code against. We pulled down the dll to the XP development boxes which allowed for compilation, but testing only on the W2K3 server. A new framework for claims based identity is in beta from Microsoft. It is code named Zermatt. One of the interesting things from the developers perspective is that with Zermatt...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

CredentialsVerificationInfo.UserValidationData.ErrorCode of 1703

Our Web SSO ADFS solution stopped authenticating users. The CredentialsVerificationExce... caught a 1703. It was not one of the "standard" ones like 87=missing user name. The SA tracked back to AD errors and the following: File Replication Service, by default, uses a randomly selected port to use for Remote Procedure Calls. Either AD or FRS started using a blocked port which caused domain authentication to fail. Solution: permanently disable the firewall
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati