Pre-release — content may change.

GuidesSingle Sign-OnDelegated Authentication

External Provider Configuration

External provider setup requirements for delegated CAS authentication

This guide covers the external provider setup requirements when using delegated CAS authentication with providers like Azure AD B2C, Auth0, and Okta.

Configuration by Wicket Team: External provider configuration is performed by Wicket implementation team, not through a self-service UI. Contact Wicket support to set up delegated authentication.

For Developers: Your application code remains unchanged when using delegated authentication. You still implement standard CAS authentication (see CAS Implementation Guide). This guide documents what you need to provide to Wicket implementation team.

Overview

When CAS is configured for delegated authentication:

  1. Application redirects user to CAS (standard CAS flow)
  2. CAS delegates authentication to external provider (transparent proxy)
  3. External Provider (B2C, Auth0, Okta) authenticates user
  4. CAS receives authentication result and translates it back to CAS protocol
  5. CAS returns service ticket with person UUID to application (standard CAS response)
  6. Application validates ticket and extracts person UUID (standard CAS flow)

Key Point: Your application sees this as standard CAS authentication. The delegation happens entirely within CAS infrastructure.

Configuration Workflow

You: Set Up External Provider

Configure your external provider (B2C, Auth0, Okta, etc.) and gather connection details:

  • Provider type and endpoints
  • Client credentials
  • Certificates (for SAML)
  • Attribute/claim mappings

You: Provide Details to Wicket Team

Send connection details and requirements to Wicket implementation team via support ticket.

Wicket Team: Configures CAS Delegation

Wicket implementation team configures:

  • External provider connection in Wicket infrastructure
  • CAS delegation to your provider
  • Attribute translation (external claims → CAS attributes)
  • Person UUID resolution

You: Set Up Middleware iPaaS

Configure middleware iPaaS to sync users:

  • Listen for Wicket webhooks (roles.granted, etc.)
  • Create/update users in external provider
  • Call /user_identities/provision to link accounts

You: Deploy Standard CAS Authentication

Your application uses standard CAS authentication (no special code for delegation).

OpenID Connect (OIDC)

Supported Providers

  • Azure AD B2C
  • Auth0
  • Okta
  • Google Identity Platform
  • Keycloak
  • Any OIDC-compliant provider

Configuration Requirements

When setting up OIDC providers, administrators need:

FieldDescriptionExample
Discovery URLOIDC discovery endpointhttps://your-tenant.b2clogin.com/.well-known/openid-configuration
Client IDOAuth client identifiera1b2c3d4-e5f6-...
Client SecretOAuth client secretsecret_abc123...
ScopesRequested scopesopenid email profile
Callback URLRedirect URI after authhttps://your-wicket.com/auth/callback

Example: Azure AD B2C

This example shows the Azure B2C configuration you'll set up and provide to Wicket implementation team.

In Azure Portal:

  1. Navigate to Azure AD B2C → App registrations
  2. Click New registration
  3. Configure:
    • Name: Wicket CAS Integration
    • Redirect URI: https://your-wicket-cas.com/oauth2/callback (CAS callback, not your app)
    • Supported account types: Accounts in this organizational directory only
  4. After creation, note:
    • Application (client) ID: 12345678-1234-...
    • Directory (tenant) ID: 87654321-4321-...
  5. Go to Certificates & secrets → Create new client secret
  6. Note the Client secret value: abc123...

User Flow Setup:

  1. Navigate to User flows → Create new user flow
  2. Select Sign up and sign in
  3. Configure attributes to collect:
    • Email address (required)
    • Given name
    • Family name
    • Object ID (for external_id)
  4. Note the user flow name: B2C_1_signupsignin

Discovery URL format:

https://{tenant-name}.b2clogin.com/{tenant-name}.onmicrosoft.com/{user-flow}/v2.0/.well-known/openid-configuration

Information to provide Wicket implementation team:

Submit a support ticket with:

Provider Type: Azure AD B2C (OpenID Connect)
Tenant Name: your-tenant
Discovery URL: https://your-tenant.b2clogin.com/your-tenant.onmicrosoft.com/B2C_1_signupsignin/v2.0/.well-known/openid-configuration
Client ID: 12345678-1234-...
Client Secret: abc123...
Scopes: openid email profile

Attribute Mappings:
- External ID: sub (OIDC subject claim)
- Email: email or emails[0]
- Given Name: given_name
- Family Name: family_name

CAS Callback URL: (Wicket team will provide this)

Wicket team will configure:

  • External provider connection
  • CAS delegation settings
  • Attribute translation (B2C claims → CAS attributes)
  • Person UUID resolution from external_id

You'll receive:

  • CAS callback URL to whitelist in Azure B2C
  • Provider slug for middleware iPaaS configuration
  • Confirmation when setup is complete

iPaaS Integration:

Middleware handles syncing users between Wicket and B2C:

// Example: iPaaS webhook handler (NOT application code)
async function handleRolesGrantedWebhook(webhookData) {
  const { person_id, email, given_name, family_name } = webhookData.person;

  // 1. Create user in B2C
  const b2cUser = await createB2CUser({
    email,
    givenName: given_name,
    surname: family_name
  });

  // 2. Link B2C user to Wicket person
  await provisionUserIdentity({
    provider_slug: 'b2c',
    external_id: b2cUser.id,  // B2C object ID
    person_id: person_id
  });

  console.log(`Provisioned B2C user ${b2cUser.id} for person ${person_id}`);
}

Provisioning Flow:

  1. Person created/updated in Wicket Admin
  2. roles.granted webhook fires to iPaaS
  3. iPaaS creates/updates B2C user account
  4. iPaaS calls /user_identities/provision to link B2C ID to Wicket person
  5. Person can now authenticate via CAS → B2C delegation

Example: Auth0

Your Auth0 Setup:

  1. Navigate to Applications → Applications → Create Application
  2. Select Regular Web Application
  3. Configure:
    • Name: Wicket CAS Integration
    • Application Type: Regular Web Application
  4. Note these details for Wicket team:
    • Domain: your-tenant.auth0.com
    • Client ID: abc123...
    • Client Secret: secret...
  5. Settings → Application URIs:
    • Allowed Callback URLs: (Wicket team will provide CAS callback URL)
    • Allowed Logout URLs: (Wicket team will provide)

Provide to Wicket Team:

Provider Type: Auth0 (OpenID Connect)
Domain: your-tenant.auth0.com
Discovery URL: https://your-tenant.auth0.com/.well-known/openid-configuration
Client ID: abc123...
Client Secret: secret...
Scopes: openid email profile

Attribute Mappings:
- External ID: sub
- Email: email
- Given Name: given_name
- Family Name: family_name

Wicket implementation team will configure delegation and provide CAS callback URL to whitelist in Auth0.

SAML 2.0

Supported Providers

  • Azure AD
  • Okta
  • OneLogin
  • Shibboleth
  • Any SAML 2.0 compliant IdP

Configuration Requirements

Provide these details to Wicket implementation team:

FieldDescription
IdP Entity IDSAML identity provider entity identifier
SSO URLSAML single sign-on endpoint
SLO URLSingle logout endpoint (optional)
X.509 CertificateIdP signing certificate (PEM format)
Metadata URLIdP metadata endpoint (if available)

Attribute Mappings:

  • External ID (NameID or specific attribute)
  • Email
  • Given name
  • Family name

Example: Okta SAML

Your Okta Setup:

  1. Applications → Create App Integration

  2. Select SAML 2.0

  3. Configure (use placeholder values, Wicket team will provide actual URLs):

    • Single sign-on URL: (Wicket team will provide CAS ACS URL)
    • Audience URI (SP Entity ID): (Wicket team will provide)
    • Attribute Statements:
      • email → user.email
      • firstName → user.firstName
      • lastName → user.lastName
      • externalId → user.id
  4. Download the X.509 Certificate

  5. Note the Identity Provider metadata URL

Provide to Wicket Team:

Provider Type: Okta (SAML 2.0)
IdP Entity ID: http://www.okta.com/exkAbc123...
SSO URL: https://your-okta.okta.com/app/abc123/sso/saml
Metadata URL: https://your-okta.okta.com/app/abc123/sso/saml/metadata
X.509 Certificate: [Attach certificate file]

Attribute Mappings:
- External ID: NameID or externalId attribute
- Email: email
- Given Name: firstName
- Family Name: lastName

Wicket implementation team will configure SAML integration and provide SP Entity ID and ACS URL to complete Okta setup.

OAuth 2.0

Custom OAuth Providers

For OAuth 2.0 providers that don't support OpenID Connect.

Information to Provide Wicket Team:

Provider Type: OAuth 2.0
Provider Name: [Your Provider]
Authorization URL: https://provider.com/oauth/authorize
Token URL: https://provider.com/oauth/token
User Info URL: https://provider.com/api/user
Client ID: your-client-id
Client Secret: your-client-secret
Scopes: user:read user:email

Attribute Mappings:
- External ID: id (from user info endpoint)
- Email: email
- Given Name: first_name
- Family Name: last_name

Callback URL: (Wicket team will provide)

Wicket implementation team will configure OAuth integration. Your application uses standard CAS authentication — CAS handles OAuth flow internally.

External CAS Providers

In some scenarios, you might integrate with an external CAS server (not Wicket's CAS) that manages authentication for another system (e.g., university CAS, corporate CAS).

Information to Provide Wicket Team:

Provider Type: CAS Protocol
CAS Server URL: https://cas.your-university.edu
CAS Version: 3.0
Service URL: (Wicket team will provide)

Attribute Mappings:
- External ID: username or uid attribute
- Email: email attribute
- Given Name: givenName attribute
- Family Name: sn or surname attribute

How it works:

  • Your app → Wicket CAS → External CAS → User authenticates → External CAS → Wicket CAS (resolves person UUID) → Your app

Wicket implementation team configures CAS-to-CAS delegation, allowing Wicket to integrate with existing CAS infrastructure while maintaining standard CAS interface for your application.

Attribute Mapping

When configuring external providers, specify how provider attributes map to Wicket person fields.

Common Mappings

Wicket FieldOIDC ClaimSAML AttributeDescription
external_idsubNameIDUnique user identifier (required)
emailemailemailEmail address
given_namegiven_namefirstNameFirst name
family_namefamily_namelastNameLast name

Custom Attribute Mappings

Include custom attribute mappings when providing details to Wicket team:

Standard Mappings:
- External ID: sub (or NameID for SAML)
- Email: email
- Given Name: given_name
- Family Name: family_name

Custom Mappings:
- Department: department claim/attribute
- Employee ID: employeeId claim/attribute
- Job Title: jobTitle claim/attribute

Wicket implementation team will configure these mappings. Middleware iPaaS automatically includes custom attributes when calling /user_identities/provision.

Testing Delegated Authentication

1. Test CAS Delegation Flow

As a developer:

  1. Implement standard CAS authentication in your application (see SSO Guide)
  2. Test with standard Wicket CAS (should work)
  3. Have administrator configure external provider delegation
  4. Test again — should work identically (CAS handles delegation transparently)

2. Verify User Can Authenticate

Test steps:

  1. Navigate to your application login
  2. Application redirects to CAS
  3. CAS detects delegation and redirects to external provider (B2C, Auth0, etc.)
  4. User authenticates with external provider
  5. External provider returns to CAS
  6. CAS translates response and returns ticket to your application
  7. Application validates ticket and extracts person UUID (standard CAS flow)
  8. User logged in successfully

3. Verify User Identity Linkage

Check that the user identity was provisioned by middleware:

GET /people/{person_id}/user_identities

Should return:

{
  "data": [{
    "type": "user_identities",
    "attributes": {
      "provider_slug": "b2c",
      "external_id": "external-user-id-from-b2c",
      "provider_type": "generic_oidc"
    }
  }]
}

Troubleshooting

Invalid Redirect URI

Error: redirect_uri_mismatch

Solutions:

  • Verify redirect URI in provider config matches exactly
  • Check for trailing slashes (/callback vs /callback/)
  • Ensure HTTPS in production

Invalid Client Credentials

Error: invalid_client

Solutions:

  • Verify Client ID and Secret are correct
  • Check credentials haven't expired or been rotated
  • Ensure correct environment (dev/staging/prod) credentials

Missing Email Claim

Error: Provisioning fails, email required

Solutions:

  • Request email scope in authorization request
  • Check attribute mapping includes email
  • Verify provider returns email in token/assertion

User Identity Not Created

Error: CAS authentication succeeds but user identity not in Wicket

Solutions:

  • Verify middleware iPaaS is receiving webhooks
  • Check iPaaS logs for provisioning errors
  • Ensure iPaaS has admin token with proper permissions
  • Verify provider_slug in iPaaS matches Wicket Admin configuration
  • Review Wicket webhook delivery logs

On this page