Overview
targetconnect supports SAML 2.0 Single Sign-On (SSO) with Shibboleth Identity Providers (IdPs). This guide covers the targetconnect settings and the changes institutions may need when migrating from the previous SSO integration.
1. Before you begin
Your IT team will need access to your Shibboleth IdP metadata and attribute release configuration, together with an operator account for the relevant targetconnect instance. We recommend testing in UAT before changing production.
In targetconnect, navigate to Maintenance > System settings > Authentication settings, select SAML as the Single-Sign-On mode and open SAML Actor Authentication Settings.
For multiple partitions, select Apply settings to all departments to apply the configuration across all partitions on this instance.
Settings must be configured separately for any partitions the operator cannot access.
Under Information to configure your SAML Enterprise Application, obtain the following values and configure them in your Shibboleth IdP:
| Setting | What to use |
| Public certificate | The certificate provided by targetconnect. |
| SAML Service Provider Entity ID | Use the exact Entity ID displayed in targetconnect, which may differ from the legacy integration. |
| ACS URL | Use the ACS URL displayed for each targetconnect service or partition. |
If separate Service Provider Entity IDs are needed for different targetconnect instances, contact targetconnect Technical Support.
3. Enter your Shibboleth IdP settings
Under Information required from your SAML Enterprise Application, use the values from your existing Shibboleth IdP metadata:
| targetconnect setting | Where to find the value |
| SAML Identity Provider Entity ID | EntityDescriptor > entityID |
| SAML login URL | SingleSignOnService with HTTP-POST binding > Location |
| SAML client certificate | IDPSSODescriptor > KeyDescriptor use="signing" > X509Certificate |
| SAML attribute name | The actual identifying SAML attribute released by your IdP, confirmed by your IT team. |
For example, metadata might contain:
For the certificate, copy the complete public signing certificate, remove XML whitespace and wrap the Base64 value in PEM headers:
-----BEGIN CERTIFICATE-----
MIIE...complete certificate Base64...
-----END CERTIFICATE-----
Use the signing certificate, not the encryption certificate. Do not provide a private key. The example XML and PEM content above are abbreviated.
Set Use case sensitive attribute matching? to No in most circumstances, unless your institution requires case-sensitive matching.
4. Check attribute release and legacy mappings
The new targetconnect SAML integration does not automatically consume UK Federation metadata. You can continue using your existing Shibboleth IdP, but its configuration must recognise the targetconnect Service Provider Entity ID and release the required identifying attribute.
When migrating from the previous integration, check:
- The attribute release policy permits the new targetconnect Service Provider Entity ID.
- The released attribute name matches the SAML attribute name configured in targetconnect.
- Legacy
HTTP_ prefixes are not retained unless they are genuinely part of the SAML attribute name. For example, a legacy HTTP_eppn mapping may now be eppn. - The released value matches the selected authentication field for the user in targetconnect.
The identifying attribute cannot necessarily be determined from IdP metadata alone. Confirm the actual attribute name and value in the SAML assertion.
In the final section of SAML Actor Authentication Settings, configure Students, Operators and, where applicable, Custom Users.
Select the targetconnect authentication field that matches the value released by the IdP. For example, an email address released by Shibboleth may be matched against a student’s University Email Address.
User-specific SAML attribute name fields can normally be left blank unless a user type requires a different attribute. Student and Operator SSO must be enabled before go-live; Custom User group SSO can be controlled individually.
6. Test the integration
Test in UAT before applying the configuration to production:
- Confirm that the IdP recognises the targetconnect Entity ID and ACS URL.
- Sign in as a test student and verify that the correct existing targetconnect account is matched.
- Repeat with an operator account and any SSO-enabled Custom User groups.
- If successful, configure production using the values shown in the production targetconnect instance.
7. Troubleshooting
| Symptom | Check |
| Authentication succeeds at Shibboleth but fails in targetconnect | Attribute release to the new Entity ID, attribute name (including any legacy HTTP_ prefix), user-field matching and case sensitivity. |
| IdP does not recognise targetconnect | The Service Provider Entity ID and ACS URL configured in Shibboleth. |
| Certificate or signature error | The complete current IdP signing certificate in PEM format, not the encryption certificate. |
| One service works but another fails | The affected service’s ACS URL and partition-specific authentication settings. |
8. Further assistance
For integration issues or separate Service Provider Entity ID requirements, contact
targetconnect.support@groupgti.com. Include your targetconnect instance, relevant Entity ID and a description of the issue. Do not send private keys.