Avkash Chauhan's Blog

Windows Azure, Windows 8, Cloud Computing, Big Data and Hadoop: All together at one place.. One problem, One solution at One time...

ACS Federation, Live ID, SAML 2.0 Support, and AppFabric Service Bus Connections Quota

ACS Federation, Live ID, SAML 2.0 Support, and AppFabric Service Bus Connections Quota

Rate This
  • Comments 1

In ACS v2 you can use Identity Provider integration i.e. Live, Google, Facebook, Yahoo, etc. if we dig deeper we find that:

  • Windows Live ID uses WS-Federation Passive Requestor Profile
  • Google and Yahoo use OpenID, including the OpenID Attribute Exchange extension.
  • Facebook uses Facebook Graph, which is based on OAuth 2.0.

 

All of above different types of identity provider can be used seamlessly with Azure ACS v2.0. Using ACS, you don't need to worry about the details of federating with each identity provider, as ACS abstracts this information away from you, making your work very simple and easy to get done.  

 

As of now ACS v2 does now support the SAML 2.0 protocol today.  For now you can try using it with “intermediation” of ADFS 2.0 service however direct SAML 2.0 support is not available. 

 

AppFabric Service Bus Connection Quota:

When exposing an on-premise service over Appfabric Service Bus, you may wonder, how many concurrent connections does service bus support? Previously, Service Bus connection limit was based on quotas which starts from 50 concurrent connections to 825 concurrent connections, depend on connection pack size purchased (e.g., pay-as-you-go, 5, 25, 100, or 500). In recent changes connection pack size is not the basis of your maximum quota. Instead all connection packs have default to 2000 concurrent connections.

 

So even if you have Connection Pack size as pay-as-you-go, 5, 25, 100, or 500 however with all the packs your connection quota will be 2000. 

Leave a Comment
  • Please add 4 and 7 and type the answer here:
  • Post
  • Good to know. Thanks Avkash

Page 1 of 1 (1 items)