{"id":284,"date":"2010-08-11T00:00:00","date_gmt":"2010-08-11T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2010\/08\/11\/windows-azure-gains-single-sign-on-support\/"},"modified":"2021-12-30T11:36:54","modified_gmt":"2021-12-30T11:36:54","slug":"windows-azure-gains-single-sign-on-support","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2010\/08\/11\/windows-azure-gains-single-sign-on-support\/","title":{"rendered":"Windows Azure Gains Single Sign-On Support"},"content":{"rendered":"<p>Microsoft has announced that the August preview release of a component of its Windows Azure AppFabric cloud computing platform adds support for federated identity and single sign-on.  The announcement was made in a blog post by Justin Smith, a Microsoft (NASDAQ: MSFT) program manager on the Windows Azure AppFabric Access Control Service (ACS) team, on Wednesday.  The ACS update should be good news for developers and service providers working on applications meant to run on Windows Azure and Windows Server as it also enables access control as a service for federating identities.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft began charging Windows Azure customers in early February, and by early June claimed to have garnered some 10,000 paying customers.  However, so far use of ACS continues to be free because it&#8217;s available via Microsoft&#8217;s AppFabric Labs environment in a manner similar to a community technology preview or CTP.<\/p>\n<p>http:\/\/itmanagement.earthweb.com\/features\/article.php\/3897451\/Windows-Azure-Gains-Single-Sign-On-Support.htm<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-284","post","type-post","status-publish","format-standard","hentry","category-cloud"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/284","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=284"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/284\/revisions"}],"predecessor-version":[{"id":2771,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/284\/revisions\/2771"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=284"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=284"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=284"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}