Claims Identity Guide–Hands On Labs

Training content based on our guides has been as popular as the content itself. You can now download the “Release Candidate” for labs corresponding to the new guide. The labs are more than just a mirror of the guide. We took the opportunity of adding a few things that complement and extend what is explained…

1

Authentication in WP7 client with REST Services–Part II

In the previous post I covered the “semi-passive” way for authentication between a Windows Phone 7 client and a REST service. This post completes the information with the “active” way. There’s nothing unexpected here really: We call the Identity Provider using a RequestSecurityToken message (RST) We send the SAML token to ACS and get a…

0

Authentication in WP7 client with REST Services–Part I

In the last drop, we included a sample that demonstrates how to secure a REST web service with ACS, and a client calling that service running in a different security realm: In this case, ACS is the bridge between the WS-Trust/SAML world (Litware in the diagram) and the REST/SWT side (Adatum’s a-Order app) This is…

2

SaaSGrid and Identity

Apprenda’s SaaSGrid is now “claims enabled”!  This is fantastic news. Any SG customer can now enjoy the benefits of claims based identity: simpler user management, easy federation with business partners, support for multiple identity providers, greater interoperability, etc. SG support for claims based identity maps nicely with what’s described in the “Claims Identity Guide –…

0

ACS as a Federation Provider – Claims transformation

To work properly, a-Order needs a number of claims to be supplied: User name Organization Role The "Organization” claim is used to filter orders belonging to a specific customer of Adatum. For example, Litware users (like Rick) will eventually end up with a token containing a claim with “Organization=Litware”. All this is done in step…

0

ACS as a Federation Provider–Home Realm Discovery Part 2

In my previous post, I had a question for all you: What would happen if Adatum’s FP didn’t supply ACS with the whr parameter? An the answer is: ….. ACS will simply ask the user!   ACS has no way (besides the whr parameter) of knowing where to go next (unless you configured your app…

0

Azure IssueTracker Enterprise - Simple Demos

Provisioning IssueTracker Enterprise: Highlights: There’s no direct interaction with Access Control Service. IssueTracker uses ACS API to create the scopes, rules and the issuer (Contoso). The provisioning form captures all the required information to setup the trust relationship between Access Controls Service and the tenant (certificate, etc)     Tenant (Contoso_Enterprise) uses IssueTracker Enterprise from…

0

Architecting Cloud Application for the Enterprise – Part V – Management

Having solved the identity issue, the SuperCloudySoftware team focuses then on the management requirements raised in the meeting with VeryBigCorp CIO. To recap, they want to: Be able to to monitor IssueTracker from their existing infrastructure, that happens to be System Center Operations Manager (SCOM) and eventually author new rules to correlate IssueTracker specific events…

2

Architecting Cloud Applications for the Enterprise – Part IV - SuperCloudySoftware sketches IssueTracker Enterprise Edition

In the previous article, we explored the challenges of building services for an enterprise, illustrating those through a dialogue between VeryBigCorp CIO and a team from SuperCloudySoftware. VBC requirements can be summarized as: Identity integration (including Single Sign On and management of access policies) Management integration (ability to monitor and act on IssueTracker from within…

3