July 2011 Update to Windows Azure AppFabric Access Control Service (ACS) 2.0 Released

Windows Azure AppFabric Access Control Service (ACS) 2.0 received a service update."All customers with ACS 2.0 namespaces automatically received this update, which primarily contained bug fixes in addition to a few new features and service changes," informs Access Control Service Product Team, including:Localization in eleven languagesIt's now available in 11 languages. Newly-supported languages include Japanese, […]

Windows Azure AppFabric Access Control Service (ACS) 2.0 received a service update.

"All customers with ACS 2.0 namespaces automatically received this update, which primarily contained bug fixes in addition to a few new features and service changes," informs Access Control Service Product Team, including:

  • Localization in eleven languages
    It's now available in 11 languages. Newly-supported languages include Japanese, German, Traditional Chinese, Simplified Chinese, French, Italian, Spanish, Korean, Russian, and Brazilian Portuguese. Users can choose their desired language from the language chooser in the upper-right corner of the portal.
  • Rules now support up to two input claims
    ACS 2.0 rules engine now supports a new type of rule that allows up to two input claims to be configured, instead of only one input claim. Rules with two input claims can be used to reduce the overall number of rules required to perform complex user authorization functions. For more information on rules with two input claims, see this article.
  • Encoding is now UTF-8 for all OAuth 2.0 responses
    In July 2011 update, the character encoding of HTTP responses is now set to UTF-8 to support extended character sets.
  • Quotas Removed
    The previous quotas on configuration data have been removed in this update. This includes removal of all limitations on the number of identity providers, relying party applications, rule groups, rules, service identities, claim types, delegation records, issuers, keys, and addresses that can be created in a given ACS namespace.

For more information, please refer to following resources:

[Via: Claims-Based Identity Blog]