This Web Application

The IDESG separates Web Sites on the Internet into the roles that create claims (Identity and Attributes Providers) and the roles that consume claims (Relying Parties). This is an example of a Relying Party web site that can interoperate with third party Identity Providers in addition to creating logins for users that do not have, or do not wish to use, external federated Identity Providers.

Source Code

is freely available at this site

IDESG Guidelines

The collections of IDESG guidelines current at the time were used to create this example of best practices.

UX Guidelines »

The list of the baseline Functional requirments the IDEF version 1.0 are used in the Self-Assesment and are referenced in links throughout this example using the same azure coloring and mouse hover tool tip as the button below.

Baseline Functional Reqs »

Mapping of roles used from the IDEF:

  1. Authenticate - This role is performed within this example for local users and in 3rd party providers if enabled.
  2. Authorize - This example, like all RPs, contain this role, some parts of which could be performed in other servers

IDESG Guidelines for business proceses

The collections of IDESG guidelines current at the time were used to create this example of best practices.

All Relying Parties shall document business polcies and proceedures for all identity functions.

Documented Processes »

NIST and the NSTIC

The origin and current direction of the National Strategy for Trusted Identities in Cyberspace.

Trusted Identities Group »
NSTIC Notes »
Origin Document »