federation

The Windows Azure Access Control Service (ACS) enables federated authentication, but all the examples I've seen has been of passive federation (browser-based applications authenticating via a sequence of HTTP redirects and scripted HTTP posts). Does the ACS support active federation ? In other words: assume that we have a rich client like a WPF or Silverlight application that accesses a web service. Is it possible to use the ACS as an STS in this scenario? Yes, this is possible. If you check the examples in the excellent Identity Training Kit or at acs.codeplex.com, you are interested in

I have ADFS server as an IdP. I have separate SP application. These are defined in circle of trust. SSO over SAML protocol is working fine. When I try SP initated log out request I got error on ADFS side : MSIS7000: The sign in request is not compliant to the WS-Federation language for web browser clients or the SAML 2.0 protocol WebSSO profile. EDIT More detail message from ADFS Event Trace : MSIS7015: This request does not contain the expected protocol message or incorrect protocol parameters were found according to the HTTP SAML protocol bindings. I have reviewed mu log out SAML message and

One of our web app would like to connect with ADFS 2.0 server to get credential token and check the user roles based on that. The ADFS server admin asked us to give them a federation metadata XML file to let them create Relying Party Trusts. I googled and only find how to download the ADFS server's federation metadata XML using URL - https:// [adfs server name] /federationmetadata/2007-06/federationmetadata.xml But could didn't find any guide to create a federation metadata XML for creating " Relying Party Trust " and " Claims Provider Trusts ". Is there a tools for creating those metadata

I have three clients each with their own RabbitMQ instances and I have an application (let's call it appA) that has its own RabbitMQ instance, the three client applications (app1, app2, app3) wants to make use of a service on appA. The service on appA requires RPC communication, app1, app2 and app3 each has a booking.request queue and a booking.response queue. With the shovel plugin, I can forward all booking.request messages from app1-3 to appA: Shovel1 virtualHost=appA, name=booking-request-shovel, sourceURI=amqp://userForApp1:password@app1-server/vhostForApp1 queue=booking.request

前言 hadoop是分布式系统，运行在linux之上，配置起来相对复杂。对于hadoop1，很多同学就因为不能搭建正确的运行环境，导致学习兴趣锐减。不过，我有免费的学习视频下载，请点击 这里 。 hadoop2出来后，解决了hadoop1的几个固有缺陷，比如单点故障、资源利用率低、支持作业类型少等问题，结构发生了很大变化，是hadoop未来使用的一个趋势。当然，配置也更加复杂，网上也没有一篇详细的教程来知道大家可以轻轻松松搭建起这个环境的。我应该算是第一个吧。 hadoop2体系结构 要想理解本节内容，首先需要了解hadoop1的体系结构。在本博客中和我的视频中都有相关内容，这里不再重复，只讲hadoop2的内容。 hadoop1的核心组成是两部分，即HDFS和MapReduce。在hadoop2中变为HDFS和Yarn。 新的HDFS中的NameNode不再是只有一个了，可以有多个（目前只支持2个）。每一个都有相同的职能。 这两个NameNode的地位如何哪？ 答：一个是active状态的，一个是standby状态的。当集群运行时，只有active状态的NameNode是正常工作的，standby状态的NameNode是处于待命状态的，时刻同步active状态NameNode的数据。一旦active状态的NameNode不能工作，通过手工或者自动切换