In order for federated identity to happen, we have to first identify the goals. In this scenario it is for the federated identity to be in place for the application Adam Buenz’s Software House offers and that ARB Security Solutions needs access to. There is one secure domain that will accept an identity from either of these two domains. No one will need any additional credentials in order to be able to access it. The Adam Buenz’s Software House issuer trusts the claims that come from them but also those that come from ARB Security Solutions employees.

There are some requirements that have to be satisfied. First, Adam Buenz’s Software House has to control access of the software component order pages. Otherwise they wouldn’t be able to allow ARB Security Solutions employees access to them. The concept of home realm discovery is involved here as that allows Adam Buenz’s Software House to find out which issuer has the credentials to do so. ARB Security Solutions will also need to make a decision about what employees are going to be able to access that software component order system.

There are few things here that need to be assumed for this scenario too. First, we assume that ARB Security Solutions has an issuer using the WS-Federation. This is important because it defines how businesses are able to share identities without breaking the boundaries of security that may be in place within their own systems.

The software component order system in use will have roles in place so that access can be controlled. This is done by having a claim in place for the type of role someone needs. There is also a value in place and that needs to be an software component order tracker. There will need to be legal documentation in place too between these two businesses so that their needs and rights are well protected. Only then can the federation legally be formed.

Article Or Research Filed Under Claims Based Authentication.

---

1 Comment »

1. [...] SharePoint Federated Identity Environment Requirements [...]

   Pingback by ARB Security Solutions » The SharePoint Federated Identity Process – Part 1 – Introduction — December 10, 2009 @ 10:16 am

RSS feed for comments on this post. TrackBack URL

Leave a comment

Name (required)

Mail (will not be published) (required)

Website