Federation Architecture

[indrajit-gsa]

Page - ficam-federation/design/01_federation_architecture.md

• Audience: Engineer/Architect
• Define the criteria for selecting design pattern.
• Specify the different architectures - stand-alone, enterprise, and federated broker.
• TFS Document section 6.2 - Developing the solution architecture has relevant content.

Preview - https://federalist-proxy.app.cloud.gov/preview/gsa/ficam-federation/23-fed-arch/design/federationarch/

[indrajit-gsa]

Image Edits: The image file for the page will require some updates.

Source file: None Image file: stand-alone.png, fed-arch.png, fed-broker.png

Suggested updates are:

• Revise the icons and box colors for the image to use 2 dimensional images.
• Change all 'CSP' to 'IdP'.
• Change all 'Application' to 'SP'.
• Do we need to mention Access Management Server? If yes, should we rename to SSO?
• Do we need the Federation Server in the image?

[indrajit-gsa]

Suggested updates based on review on March 5th 2018:

• Revise the introduction to each of these architectures. Does a decision tree make more sense than a table? Possibly not easy to provide a decision tree since the differences between enterprise vs broker are often confusing. An enterprise federation server can also act as a federation broker.
• Review the examples for each type of federation architecture. The example for Defense Support for Civil Authorities in FICAM Roadmap 12.1.2 for Point-to-Point may not apply any more. Provide example of a Federal enterprise federation implementation. Max.gov will apply to broker architecture.
• Broker architecture - Separate out max.gov into alert box to stand out from the other text.