Get started with OpenID Federation

Use OpenID Federation to establish trust for any digital ecosystem, including Open Data, wallets, Agentic AI access, and more. Raidiam Connect enables you to:

• Create the simplest federations with a single Trust Anchor

• Create a federation of federations, where there are multiple Trust Anchors, either internal only or including external ones

• Use a Raidiam Connect Trust Anchor as an intermediate Trust Anchor in an existing external federation

Request sandbox access

Request sandbox access to create an OpenID Federation with Raidiam Connect.

Create an OpenID Federation Trust Anchor

Create an OpenID Federation by adding a federation record in Reference Data. This creates your Trust Anchor and its associated federation endpoints.

Add domains and roles

1. Create a domain and associate it with the federation you created.

   Domains control which roles are available for organizations and their technical resources within the federation.

2. Add roles and their metadata within the domain you created.

   Federation-type roles define how an organization's client application or RP metadata, and authorization server or OP metadata, are presented to the broader ecosystem.

Configure Intermediate Federation Entities (Optional)

If you are creating a federation with multiple levels of authority, you can configure Intermediate Entities either by creating another federation that references your superior Trust Anchor, or by configuring an organisation as an authority.

Onboard organizations

1. Add Organizations to participate in the federation.

2. Assign the domain associated with the federation to the onboarded organizations.

3. Assign roles to organizations.

4. Delegate organization Administration, enabling organization administrators to register their technical resources like applications or servers.

   
   

tip

Once an organization administrator registers a client application and assigns a federation-type role to this client, it receives a unique entity identifier and is treated as a federation participant. This means it is listed in the federation's /list endpoint. Authorization servers can then use your federation's /fetch endpoint to get signed Entity Configurations for that client, or use the federation's /resolve endpoint to resolve the full Trust Chain.

If the organization administrator registers an authorization server/OP, it is added automatically to the federation (available in the /list endpoint) based on the organization's domain assignment, unless it is explicitly set not to participate in the ecosystem or federation during server creation.