A Lap Around the Windows Azure AppFabric
•Descargar como PPTX, PDF•
0 recomendaciones•699 vistas
Learn how to use services in the Windows Azure AppFabric (such as Service Bus, Access Control, and Caching) as building blocks for Web-based and Web-hosted applications, and how developers can leverage these services to create and extend applications in the cloud while also connecting them with on-premises systems.
Recomendados
Recomendados
Más contenido relacionado
Destacado
Destacado (19)
Más de Wade Wegner
Más de Wade Wegner (8)
Último
Último (20)
A Lap Around the Windows Azure AppFabric
- 8. Caching Service Bus Access Control Integration Composite App (WF, WCF)
- 22. Datacenter LOB web service LOB app Partner Mobile Device SB ACS
- 23. Datacenter LOB web service LOB app Partner Mobile Device SB ACS
- 24. Datacenter LOB web service LOB app Partner Mobile Device SB ACS
- 25. Partner Mobile Device Datacenter LOB web service LOB app SB ACS
- 29. CTP Caching PDC9/16 CTP Access Control enhancements H1 2011 General Availability Caching CTP Composite App General Availability Access Control CTP Service Bus enhancements Release Service Bus enhancements TechEd EMEA
Notas del editor
- Relying Party - In identity jargon, we often refer to applica-tions as “Relying Parties,” an expression that refers to the fact that the application relies on one or more IPs to take care of authentication on their behalf Identity Providers – The party that stores user identities e.g. AD, Live ID, Google, etc. Token – Claim – an attribute that’s a part of the token,
- The Client (in this case a browser) requests a resource at the RP. In most cases, this is simply an HTTP GET. Since the request is not yet authenticated, the RP redirects the Client to the correct IdP. The RP may determine which IdP to redirect the Client to using the Home Realm Discovery capabilities of ACS. The Client browses to the IdP authentication page, and prompts the user to login. After the Client is authenticated (e.g. enters credentials), the IdP issues a token. After issuing a token, the IdP redirects the Client to ACS. The Client sends the IdP issued token to ACS. ACS validates the IdP issued token, inputs the data in the IdP issued token to the ACS rules engine, calculates the output claims, and mints a token that contains those claims. ACS redirects the Client to the RP. The Client sends the ACS issued token to the RP. The RP validates the signature on the ACS issued token, and validates the claims in the ACS issued token. The RP returns the resource representation originally requested in (1).