Federation för kommunal verksamhet (Fedkom) enables federated authentication and attribute exchange between Swedish municipalities and service providers delivering digital services to the municipal sector.
Participating municipalities use their own Identity Provider (IdP) to authenticate users. Service providers connect their services as Service Providers (SPs) and can rely on the identities and attributes provided through the federation.
Fedkom provides a common framework for trust, technical requirements and SAML metadata exchange. The federation is not technically limited to a specific digital service and may support additional services intended for Swedish municipalities.
Scope
Participation in Fedkom is intended for:
- Swedish municipalities acting as Identity Providers (IdPs); and
- service providers delivering digital services to Swedish municipalities.
Other public-sector organizations, such as government agencies and regions, are not within the scope of Fedkom as user organizations.
An organization must have signed the applicable Fedkom membership agreement before joining the federation.
Start here
The appropriate connection process depends on whether you represent a municipality or a service provider.
Municipalities
Municipalities connect an Identity Provider (IdP) to enable their users to authenticate to services available through Fedkom.
Start with the Technical Metadata Connection Guide (Fedkom). The guide explains how to:
- prepare and validate IdP metadata;
- apply the required entity attribute;
- select the appropriate publication path;
- publish metadata through Federationsadmin, where applicable; or
- submit metadata manually to the federation operator.
Service providers
Service providers connect a Service Provider (SP) to make their service available to participating municipalities.
SP metadata is submitted manually to the federation operator. The Technical Metadata Connection Guide (Fedkom) describes the metadata requirements, validation process and submission procedure.
Connection process
Connecting an entity to Fedkom normally involves the following steps:
- Sign the applicable Fedkom membership agreement.
- Review the federation policy and applicable technical requirements.
- Prepare and validate the organization’s SAML metadata.
- Publish or submit the metadata using the appropriate connection path (See Technical Metadata Connection Guide (Fedkom)).
- Configure the IdP or SP to consume and verify the Fedkom metadata feed (See SAML Federation (Fedkom)).
Publication of an entity in the Fedkom metadata feed establishes the technical federation connection. It does not, by itself, grant access to services available through the federation. Individual services may have additional agreements, authorization requirements and configuration instructions.
Accessing KLASSA through Fedkom
KLASSA is currently the service available through Fedkom. Swedish municipalities use their Fedkom-connected Identity Provider (IdP) to enable federated access to KLASSA.
Connecting and publishing an IdP in Fedkom completes only the federation-specific part of the setup. To access KLASSA, the municipality must also:
- configure its IdP for the KLASSA Service Provider (SP);
- release the attributes and authorization information required by KLASSA; and
- complete the service-specific setup and testing described by Adda.
Follow Adda’s Åtkomstvägledning för KLASSA 5 and Vägledning för administratörer av KLASSA 5, available on the KLASSA 5 guidance page.
Documentation
Federation policy
The Federation Policy for Fedkom defines the conditions for participation and the technical and trust-related requirements that apply within the federation.
Technical Metadata Connection Guide
The Technical Metadata Connection Guide (Fedkom) explains how municipalities and service providers prepare, validate and publish their SAML metadata. This is the main starting point for connecting an entity to Fedkom.
Environments and operational information
The SAML Federation (Fedkom) section provides information about the federation environments, including metadata feeds, signing certificates and other details required when configuring an IdP or SP.