Tutorials

• Rancher-SAML-ADFS (Authentik)
• Organizr LDAP Setup (Authentik)
• LDAP Provider Generic Setup (Authentik)
• Steps to configure SAML 2.0 SSO with Microsoft Active Directory Federation Services
• iSpring Learn SSO with Azure AD + SAML
• Setting-up Azure Entra with Classlink
• Classlink LTI v1.3 (OIDC) Details
• Disable MFA in EntraID (Azure AD)

Rancher-SAML-ADFS (Authentik)

What is Rancher​

An enterprise platform for managing Kubernetes Everywhere Rancher is a platform built to address the needs of the DevOps teams deploying applications with Kubernetes, and the IT staff responsible for delivering an enterprise-critical service.

-- https://rancher.com/products/rancher

Preparation​

The following placeholders will be used:

• rancher.company is the FQDN of the Rancher install.
• authentik.company is the FQDN of the authentik install.

Under Customization -> Property Mappings, create a SAML Property Mapping. Give it a name like "SAML Rancher User ID". Set the SAML name to rancherUidUsername and the expression to the following

return f"{user.pk}-{user.username}"

Create an application in authentik. Set the Launch URL to https://rancher.company, as Rancher does not currently support IdP-initiated logins.

Create a SAML provider with the following parameters:

• ACS URL: https://rancher.company/v1-saml/adfs/saml/acs
• Audience: https://rancher.company/v1-saml/adfs/saml/metadata
• Issuer: authentik
• Service Provider Binding: Post
• Property mappings: Select all default mappings and the mapping you've created above.
• Signing Certificate: Select the authentik self-signed certificate.

You can of course use a custom signing certificate, and adjust durations.

Rancher​

In Rancher, navigate to Global -> Security -> Authentication, and select ADFS.

Fill in the fields

• Display Name Field: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name
• User Name Field: http://schemas.goauthentik.io/2021/02/saml/username
• UID Field: rancherUidUsername
• Groups Field: http://schemas.xmlsoap.org/claims/Group

For the private key and certificate, you can either generate a new pair (in authentik, navigate to Identity & Cryptography -> Certificates and select Generate), or use an existing pair.

Copy the metadata from authentik, and paste it in the metadata field.

Click on save to test the authentication.

Organizr LDAP Setup (Authentik)

Support level: Community

What is organizr​

Organizr allows you to setup "Tabs" that will be loaded all in one webpage.

-- https://github.com/causefx/Organizr

This integration leverages authentik's LDAP for the identity provider to achieve an SSO experience. See ldap provider generic setup for setting up the LDAP provider.

Preparation​

The following placeholders will be used:

• organizr.company is the FQDN of the Service install.
• authentik.company is the FQDN of the authentik install.

Create a new user account (or reuse an existing) for organizr to use for LDAP bind under Directory -> Users -> Create, in this example called ldapservice.

Note the DN of this user will be cn=ldapservice,ou=users,dc=ldap,dc=goauthentik,dc=io

Optionally, create a new group like organizr users to scope access to the organizr application.

Authentik Configuration​

1. Create a new Proxy Provider for https://organizr.company  Optionally, add the regular expression to allow api calls in the advanced protocol settings. 
2. Create a new Application for the https://organizr.company Provider. 
   
   

   TIP
   Optionally, bind the group to control access to the organizr to the application. 

3. 

 ::: 3. Add the Application to the authentik Embedded Outpost.

organizr Configuration​

CAUTION
Ensure any local usernames/email addresses in organizr do not conflict with usernames/email addresses in authentik.

1. Enable Auth Proxy in organizr system settings -> main -> Auth Proxy

Auth Proxy Header Name: X-authentik-username Auth Proxy Whitelist: your network subnet in CIDR notation IE 10.0.0.0/8 Auth Proxy Header Name for Email: X-authentik-email Logout URL: /outpost.goauthentik.io/sign_out 

2. Setup Authentication in organizr system settings -> main -> Authentication

Authentication Type: Organizr DB + Backend Authentication Backend: Ldap Host Address: <LDAP Outpost IP address:port> Host Base DN: dc=ldap,dc=goauthentik,dc=io Account Prefix: cn= Account Suffix: ,ou=users,dc=ldap,dc=goauthentik,dc=io Bind Username: cn=ldapservice,ou=users,dc=ldap,dc=goauthentik,dc=io Bind Password: <LDAP bind account password> LDAP Backend Type: OpenLDAP 

INFO
Access for authentik users is managed locally within organizr under User Management. By default, new users are assigned the User group.

TIP
Consider front-ending your application with a forward auth provider for an SSO experience.

LDAP Provider Generic Setup (Authentik)

Create User/Group​

1. Create a new user account to bind with under Directory -> Users -> Create, in this example called ldapservice.

   Note the DN of this user will be cn=ldapservice,ou=users,dc=ldap,dc=goauthentik,dc=io

2. Create a new group for LDAP searches. In this example ldapsearch. Add the ldapservice user to this new group.NFO

Note: The default-authentication-flow validates MFA by default, and currently everything but SMS-based devices are supported by LDAP. If you plan to use only dedicated service accounts to bind to LDAP, or don't use SMS-based authenticators, then you can use the default flow and skip the extra steps below and continue at Create LDAP Provider

LDAP Flow​

Create Custom Stages​

1. Create a new identification stage. Flows & Stage -> Stages -> Create 
2. Name it something meaningful like ldap-identification-stage. Select User fields Username and Email (and UPN if it is relevant to your setup). 
3. Create a new password stage. Flows & Stage -> Stages -> Create 
4. Name it something meaningful like ldap-authentication-password. Leave the defaults for Backends. 
5. Create a new user login stage. Flows & Stage -> Stages -> Create 
6. Name it something meaningful like ldap-authentication-login. 

Create Custom Flow​

1. Create a new authentication flow under Flows & Stage -> Flows -> Create, and name it something meaningful like ldap-authentication-flow 
2. Click the newly created flow and choose Stage Bindings. 
3. Click Bind Stage choose ldap-identification-stage and set the order to 10. 
4. Click Bind Stage choose ldap-authentication-login and set the order to 30. 
5. Edit the ldap-identification-stage. 
6. Change the Password stage to ldap-authentication-password. 

Create LDAP Provider​

1. Create the LDAP Provider under Applications -> Providers -> Create. 
2. Name is something meaningful like LDAP, bind the custom flow created previously (or the default flow, depending on setup) and specify the search group created earlier. 

Create LDAP Application​

1. Create the LDAP Application under Applications -> Applications -> Create and name it something meaningful like LDAP. Choose the provider created in the previous step. 

Create LDAP Outpost​

1. Create (or update) the LDAP Outpost under Applications -> Outposts -> Create. Set the Type to LDAP and choose the LDAP application created in the previous step. 
   

   INFO
   The LDAP Outpost selects different providers based on their Base DN. Adding multiple providers with the same Base DN will result in inconsistent access

ldapsearch Test​

Test connectivity by using ldapsearch.

INFO
ldapsearch can be installed on Linux system with these commands

sudo apt-get install ldap-utils -y # Debian-based systems
sudo yum install openldap-clients -y # CentOS-based systems

ldapsearch \
  -x \
  -h <LDAP Outpost IP address> \
  -p 389 \ # Production should use SSL 636
  -D 'cn=ldapservice,ou=users,DC=ldap,DC=goauthentik,DC=io' \
  -w '<ldapuserpassword>' \
  -b 'DC=ldap,DC=goauthentik,DC=io' \
  '(objectClass=user)'

To deploy an outpost with docker-compose, use this snippet in your docker-compose file.

You can also run the outpost in a separate docker-compose project, you just have to ensure that the outpost container can reach your application container.

Proxy outpost​

version: "3.5"

services:
    authentik_proxy:
        image: ghcr.io/goauthentik/proxy
        # Optionally specify which networks the container should be
        # might be needed to reach the core authentik server
        # networks:
        #   - foo
        ports:
            - 9000:9000
            - 9443:9443
        environment:
            AUTHENTIK_HOST: https://your-authentik.tld
            AUTHENTIK_INSECURE: "false"
            AUTHENTIK_TOKEN: token-generated-by-authentik
            # Starting with 2021.9, you can optionally set this too
            # when authentik_host for internal communication doesn't match the public URL
            # AUTHENTIK_HOST_BROWSER: https://external-domain.tld

LDAP outpost​

version: "3.5"

services:
    authentik_ldap:
        image: ghcr.io/goauthentik/ldap
        # Optionally specify which networks the container should be
        # might be needed to reach the core authentik server
        # networks:
        #   - foo
        ports:
            - 389:3389
            - 636:6636
        environment:
            AUTHENTIK_HOST: https://your-authentik.tld
            AUTHENTIK_INSECURE: "false"
            AUTHENTIK_TOKEN: token-generated-by-authentik

Steps to configure SAML 2.0 SSO with Microsoft Active Directory Federation Services

Note: ADFS 2.0 on Windows Server 2008 r2 or ADFS 3.0 on Windows Server 2012 / 2012 r2)

SAML 2.0 single sign-on (SSO) supports integration with Microsoft Active Directory Federation Services (ADFS) 3.0.

Requirements

In this example we are using ADFS 2.0 on Windows Server 2008 R2. On Windows Server 2012 the steps will be the same except for the installation, because you install AD FS role via the server manager, not via the installation package as on Windows 2008 server r2.

Step 1. AD FS Management

Login in to your AD FS server and launch the ADFS Management Console via the shortcut in Control Panel\Administrative Tools.

Step 2. Check AD FS settings

Right-click on Service and sel ect Edit Federation Service Properties...

Confirm that the General settings match your DNS entries and certificate names. Make a note with the Federation Service Identifier, since that is used in the iSpring Learn SAML 2.0 configuration settings.

Step 3. Token-Signing certificate

Step 4. Learn Settings

Step 5. ADFS Relying Party Configuration

Go to the ADFS Management console and select Relying Party Trusts, right-click on it and select Add Relying Party Trust…

Select Next On the Welcome Screen of the wizard, and on the Select Data Source step, select the last option: Enter data about the relying party manually.

On the next screen, enter a Display name that you will recognize in the future.

Next, select AD FS profile:

Leave the default values:

On the next screen, check the box labeled: Enable support for the SAML 2.0 WebSSO protocol. The service URL will be: https://YourAccоuntURL.ispringlearn.com/module.php/saml/sp/saml2-acs.php/default-sp

Click Next. Add Relying party trust identifier:  https://YourAccоuntURL.ispringlearn.com/module.php/saml/sp/metadata.php/default-sp

Choose Permit all users to access this relying party.

On the next step, just click Next.

On the final screen, check the box Open the Edit Claim Rules dialog and use the Close button to exit.

Step 6. Creating Claims Rules

Step 7. Adjusting the Trust Settings

Some settings on your Relying Party Trust will need to be adjusted. To access these settings, select Properties from the Actions sidebar on the right while you have the Relying Party Trust selected.

Step 8. Logging

Go to your SSO login page: https://YourAccоuntURL.ispringlearn.com/sso/login and enter your credentials.

Related Articles

• Integrating iSpring Learn with your system: User Management and Single Sign On
• SAML Technology for SSO
• iSpring Learn SSO with Azure AD + SAML

iSpring Learn SSO with Azure AD + SAML

Azure Active Directory (Azure AD) is a part of the Microsoft Azure cloud service that makes it possible to enjoy SSO (Single sign-on) without employing on-prem AD FS (Active Directory Federated Services). It is basically a cloud alternative to Microsoft Active Directory. In this scenario, there is no need to maintain an on-premise infrastructure, the process of setting it up is rather easy, and it works with most cloud-based services.

Requirements

A Microsoft Azure account with Azure AD Premium activated.

How to set up Azure AD

In the right-side menu, fill out Identifier (Entity ID), Reply URL, and Relay state as shown in the table below, where ‘_____’ is the first part of the URL of your iSpring Learn account. Pay attention to the domain for your iSpring Learn account: it is either .com or .eu.

Save the changes. 

1. Second, select 

Edit 

1. to edit User Attributes and Claims.

The first claim in the list is the Required claim. Its claim name is Unique User Identifier (Name ID) and its Value is user.mail. It is there by default. Leave it as it is.
The additional claims are those used by iSpring Learn to sync the data about your users and fill out their user profiles in iSpring Learn. The information will be updated in iSpring Learn each time you log in.

Claim Name	Value
user.login	user.mail
user.mail	user.mail
user.surname	user.surname
user.givenname	user.givenname
user.jobtitle	user.jobtitle

1. Only the Name and the Source Attribute fields need to be changed. Leave the rest empty.

1. When you are done, you should see the list of all the claims you want your iSpring Learn account to be in sync with.

Note that you won’t be able to sync the user’s country and department.

Related Articles

• SAML Technology for SSO
• Integrating iSpring Learn with your system: User Management and Single Sign On
• How to upload SCORM courses to ...

Setting-up Azure Entra with Classlink

Notes

This is an all or none type of configuration. Once enabled all users of the domain will be redirected to Launchpad for authentication in all Microsoft applications. Users previously Authenticated to Office 365/Entra ID (Azure AD) may need to reauthenticate their desktop applications. Office365 Administrator accounts will not be affected by this workflow.

Prerequisites

• Authenticate to LaunchPad with AD (technically could be Google as well but unlikely)
  • • District’s Azure user profile must contain an ImmutableI   
    • If the district uses Azure AD Connect, it’s handled  
    • If the district enters users manually, it’s handled  
    • If the district uses OneSync for Azure, it can be handled in the configuration
• Add Verified Domain to Entra ID (Azure AD)
  •  Do not make it primary.
• Install MSOnline PowerShell module 

  Install-Module MSOnline

• Install Azure Active Directory Connect and configure it – Do not federate via this method.
•  Active Directory should be connected in launchpad under settings > domain gear icon
•  Active Directory Groups should be imported into launchpad

Step 1

1.       In the Classlink tenant SAML Console, Create a new SAML configuration by copying existing and selecting “A New SAML App (template)”

2.       Configure the following options.

• Metadata URL
  •         https://nexus.microsoftonline-p.com/federationmetadata/saml20/federationme tadata.xml
• Loginurl with custom login, e.g. https://launchpad.classlink.com/<customurl>
•  Attribute Mapping
• ▪          Select “Custom Attribute”
  • • Change name of the custom attribute to “IDPEmail”
    •  Add {email} in the data field
• MetaOverrides
  •    Logout Service URL (POST)
    • • •   https://login.microsoftonline.com/common/oauth2/logout
  • NamedID Format
    • • •  Persistent
  • NameID Custom Value
    • • • {ldapguid:hexbase64}
•  Save or Update

Step 2

•  Copy the metadata URL and modify the PowerShell Script below
•  Use this PowerShell Script, change the file extension to “.ps1” after downloading - You may need to unblock the file and change your execution policy on the server
  •  Google Drive

<#
.SYNOPSIS
    Federate Microsoft Entra ID (Azure AD/Microsoft Online Services) to ClassLink for IdP Services.

    Change the <GUID> in the $idpMetadataUrl to be the GUID from your SAML console App.
    Change $DomainName to match your domain name that is going to be Federated
    Change the script extension to ".ps1"

    *NOTE: you may need to set the PowerShell Execution Policy to remote signed or bypass temporarily.

#>

Install-Module -Name MSOnline
Import-Module MSOnline

$idpMetadataUrl = "https://idp.classlink.com/sso/metadata/<GUID>"

$DomainName = "<your domain name>"
$metadataxml = [Xml](Invoke-WebRequest -Uri $idpMetadataUrl -ContentType "application/xml").content

$cert = -join $metadataxml.EntityDescriptor.IDPSSODescriptor.KeyDescriptor.KeyInfo.X509Data.X509Certificate.Split()
$issuerUri = $metadataxml.EntityDescriptor.entityID
$logOnUri = $metadataxml.EntityDescriptor.IDPSSODescriptor.SingleSignOnService | ? { $_.Binding.Contains('Redirect') } | % { $_.Location }
$LogOffUri = $metadataxml.EntityDescriptor.IDPSSODescriptor.SingleLogoutService | ? { $_.Binding.Contains('Redirect') } | % { $_.Location }
$brand = "ClassLink Identity"
Connect-MsolService
$DomainAuthParams = @{
    DomainName = $DomainName
    Authentication = "Federated"
    IssuerUri = $issuerUri
    FederationBrandName = $brand
    ActiveLogOnUri = $logOnUri
    PassiveLogOnUri = $logOnUri
    LogOffUri = $LogOffUri
    SigningCertificate = $cert
    PreferredAuthenticationProtocol = "SAMLP"
}

Set-MsolDomainAuthentication @DomainAuthParams

 If you receive an error regarding scripts being disabled Open an elevated PowerShell prompt Type the following:
 set-executionpolicy remotesigned -force
This will allow local PowerShell scripts to run

●     If you use an account that is being federated (using the custom domain instead of an onmicrosoft.com domain) https://portal.azure.com should redirect you to https://launchpad.classlink.com/<customurl> for login from now on, along with any other Microsoft Service

Step 3:

●     Make sure you have break-glass accounts within Microsoft in case something happens.

○     https://learn.microsoft.com/en-us/azure/active-directory/roles/security-emergency-acc ess

Revert to Entra ID (Azure AD) Managed Authentication

Open PowerShell

1. Run the command
2. Connect-MsolService

After authenticating to your Entra ID (Azure AD) Tenant

 Run the command:

  Set-MsolDomainAuthentication -authentication managed -domainName
<domainname>

Replace <domainname> with your domain you wish to remove federation

Classlink LTI v1.3 (OIDC) Details

Dear Vendor,

Our school is going to add your app as an LTI v1.3 SSO app through ClassLink. Please provide me with the following information:

·         ClientID (generated in the Partner Portal)

·         OIDC Login Initiation URL

·         Target Link URL

·         LTI Message Type (default is LtiResourceLinkRequest)

·         Person SourcedID

·         Role

·         With PII

·         Any Input Fields that I would need

Here is information about our school system and ClassLink:

·         The OpenID Connect (OIDC) discovery endpoint is https://launchpad.classlink.com/.well-known/openid-configuration 

·         The OIDC discovery endpoint contains the following:

o   Issuer ID: https://launchpad.classlink.com

o   OIDC URL: https://launchpad.classlink/com/oauth2/v2/auth

o   JWKS URL: https://launchpad.classlink/com/oauth2/v2/jwks

·         Our SchoolDeployment ID (Tenant ID) is xxxx. (Not all vendors require a Deployment ID, but it's best to include it in case it is needed.)

Thank you so much for your help with this,

Insert Your Name and Contact Information

Disable MFA in EntraID (Azure AD)