* website/integrations: rename "Create with Provider" to "New Application" The application list page now uses a split-button labeled "New Application" instead of the old "Create with Provider" dropdown. Update all 113 integration guides to match. * website/docs: update flow, stage, and policy button labels - "Create" → "New Flow", "New Stage", "New Policy" for trigger buttons - "Finish" → "Create Flow", "Create Stage", "Create Policy" for submit - "Create and bind stage" → "New Stage" / "Bind Existing Stage" - "Create" (binding submit) → "Create Stage Binding" * website/docs: update provider button labels - "Create" → "New Provider" for trigger buttons - "Create with Provider" → "New Application" in RAC docs - "Create" → "New Property Mapping", "New RAC Endpoint", "New Prompt" for related entity creation * website/docs: update directory button labels - "Create" → "New Source" for federation/social login pages - "Create" → "New Role", submit → "Create Role" - "Create" → "New Invitation" - Policy binding submit → "Create Policy Binding" * website/docs: update endpoint device and system management button labels - "Create" → "New Endpoint Connector", "New Enrollment Token", "New Device Access Group", "New Flow" - Submit → "Create Device Access Group" - "Create" → "New Notification Rule", "New Notification Transport" - Binding submit → "Create Policy Binding" * Reorganize policy documentation * website/docs: address policy docs review feedback * post-rebase * website/docs: Reorganize policy documentation -- Revisions (#21601) * apply suggestions * Fix escaped. * Fix whitespace. * Update button label. * Fix phrasing. * Fix phrasing. * Clean up stragglers. * Format. --------- Co-authored-by: Dominic R <dominic@sdko.org>
3.2 KiB
title, tags
| title | tags | |||
|---|---|---|---|---|
| Shibboleth |
|
Allows users to authenticate using their Shibboleth credentials by configuring Shibboleth as a federated identity provider via SAML.
Preparation
The following placeholders are used in this guide:
authentik.companyis the FQDN of the authentik installation.shibboleth.companyis the FQDN of the Shibboleth IdP installation.shibboleth-slugis the slug you will assign to the SAML source in authentik (e.g.,shibboleth).
authentik configuration
To integrate Shibboleth with authentik you will need to create a SAML source in authentik.
Create a SAML source in authentik
- Log in to authentik as an administrator and open the authentik Admin interface.
- Navigate to Directory > Federation and Social login and click New Source.
- Select SAML Source and configure the following settings:
- Set Name to
Shibboleth. - Set Slug to
shibboleth(this sets the slug used in Shibboleth's metadata url). - Set SSO URL to
https://shibboleth.company/idp/profile/SAML2/Redirect/SSO. - Set Binding Type to
Redirect. - Set Issuer to
https://authentik.company/source/saml/<shibboleth-slug>/metadata/. - Set NameID Policy to
Transient. :::warning NameID Policy Shibboleth supports theTransientNameID by default. You will need to reconfigure Shibboleth to use other NameIDs. ::: - Set Signing Keypair to an authentik certificate (e.g., the default
authentik Self-signed Certificate). - Set Encryption Certificate to an authentik certificate (e.g., the default
authentik Self-signed Certificate).
- Set Name to
- Click Finish.
:::info Display new source on login screen For instructions on how to display the new source on the authentik login page, refer to the Add sources to default login page documentation. :::
:::info Embed new source in flow :ak-enterprise For instructions on embedding the new source within a flow, such as an authorization flow, refer to the Source Stage documentation. :::
Shibboleth configuration
To integrate Shibboleth with authentik you will need to add authentik as a service provider in your Shibboleth IdP.
Add authentik as a Service Provider
- Edit
/opt/shibboleth-idp/conf/metadata-providers.xmlon the Shibboleth IdP server. - Add the following
MetadataProviderelement before the final closing tag of the existingMetadataProviderblock:
<MetadataProvider id="Authentik"
xsi:type="FileBackedHTTPMetadataProvider"
backingFile="%{idp.home}/metadata/authentik-metadata.xml"
metadataURL="https://authentik.company/source/saml/<shibboleth-slug>/metadata/" />
- Restart the Shibboleth IdP to apply the changes.
Source property mappings
Source property mappings allow you to modify or gather extra information from sources. See the overview for more information.