Skip to main content

Step 4: Customize the Sample Service Provider Metadata File

This step customizes the sample Service Provider metadata file for your Code Insight server.

To customize the sample Service Provider metadata file, do the following:

  1. In a text editor, open the SCA_install_home``/config/core/security/SPMetadata.xml file.

  2. Update the following properties, and save the file:

    SSO PropertyDescription
    entityID="ENTITY_VALUE"Replace ENTITY_VALUE with the same entity ID as the one you provided the env\.properties file in Step 2: Prepare the Environment Properties File.
    SingleLogoutService... FULLY_QUALIFIEDHOSTNAME...Replace FULLY\_QUALIFIEDHOSTNAME with the fully qualified hostname of the Code Insight server.
    AssertionConsumerService... FULLY_QUALIFIEDHOSTNAME...Replace FULLY\_QUALIFIEDHOSTNAME with the fully qualified hostname of the Code Insight server.
    requestSignedSet to true to indicate that the Service Provider must sign authentication requests.
    wantAssertionSignedSet to true to indicate that the Service Provider requires signed assertions received from Identity Provider.

Starting in the Code Insight 2025 R4, the application no longer uses the SPMetadata.xml file at runtime. Instead, all necessary Service Provider metadata is dynamically generated based on the values specified in the core.sso.common.properties file. As a result, manual creation or editing of the SPMetadata.xml file is no longer required when configuring SSO in current versions.

However, some Identity Providers may still require the SPMetadata.xml file during the initial SSO integration process. In such cases, even though the application does not rely on it at runtime, you can manually generate or update the file using the metadata values configured in your environment.

Alternatively, you can download the dynamically generated metadata directly from the application using this URL: https://<FULLY_QUALIFIED_HOSTNAME>:8443/codeinsight/saml2/service-provider-metadata/<REGISTRATION_ID>

note

The REGISTRATION_ID must match the value that is set for the saml.registration.id property in the core.sso.common.properties file.