You are located in service: Identity Management

ServiceProviderManager

ServiceProviderManager

guide

The ServiceProviderManager (SPM) is the central tool for managing local RWTH services connected to the RWTH IdentityProvider (IdP) and authenticated via RWTH Single Sign-On. It is intended for both technical administrators and individuals responsible for technical or organizational matters.

This page explains how to maintain your own services (ServiceProviders) in the SPM, view configured attributes, and manage administrative contacts.

 

Please note

To request a new ServiceProvider, follow the instructions on the Connecting a Shibboleth ServiceProvider page. The IT Center will create the ServiceProvider and fill in the necessary fields, such as EntityId and Organization.

Overview of the homepage

The ServiceProviderManager homepage is accessible without login.

On the homepage, you will find the following:

  • a directory of all local services connected via the RWTH IdentityProvider;
  • an overview of all DFN-AAI services with special attribute activations;
  • the respective contact persons for questions regarding usability.

The following information is displayed for each ServiceProvider:

Screenshot of the ServiceProviderManager Homepage. The ServiceProviders are listed in a table. There is a search bar above the table. The table has 6 columns: Service, Description, Requested Attributes, EntityId, Organisation, and Contact.

Service

Each ServiceProvider has a clear service name assigned by the responsible organization.

Description

The description should be detailed enough to give users an idea of whether the service is relevant to them. It should explain the purpose of the ServiceProvider.

Please note:
If a service consists of several providers, take a look at how IdM Selfservice is structured for an example of how to organize your description.

Requested Attributes

The SPM displays all the attributes transmitted by the IdentityProvider to the service when a person logs in. Technical details can be found on the Explanation of attributes page.

For example, the following attributes can be transmitted:

Screenshot of a table from the "Explanation of attributes" page. Examples of attributes are: Address: Postal code, street, academic titles before or after the name, anonymized global ID.

EntityId

The EntityId is a ServiceProvider's technical identification number. It is required for support requests, among other things.

The IT Center sets it.

Organization

This column shows which organization operates or is responsible for the service.

The IT Center fills it out.

Contact

At least one administrative contact must be entered. This information is publicly visible. This allows users to ask the ServiceProvider questions about its content and technical aspects.

Access for administrators

There are two ways to access the SPM:

Role-based access

Access to administration is granted via the "RWTH SSO Service Provider Administration" role.

The IT Center activates this role for the organization during the registration process.

Then, the organization's role manager can assign the role to you as ServiceProvider administrator.

After redeeming the role coupon, you can log in to SPM via RWTH Single Sign-On to manage your ServiceProvider.

Screenshot of the SPM home page. The Login button is located in the menu bar, before the language selection.

Delegation via groups

Organizations with many services can delegate administration via groups set up in the IdM role and group management.

To do this, someone with access to the SPM must log in and follow these steps:

Step 1
Find the desired ServiceProvider in the table on the homepage. Then, click on the pencil icon in the "Edit" column.

Screenshot of the SPM after logging in. Two additional columns are now displayed in the table after the Contact column: "Status" and "Edit."

Step 2
Click Organization.

Step 3
Add the group under "Groups".

Step 4
Click Save and Continue.

Screenshot of the Organization tab. The page is divided into three sections: Organization, Groups, and ContactPerson. The Groups section displays the groups that have already been added. Below that, you can select new groups. The Save and Continue button is located below the Contact Person section.

Please note:

  • Groups must already exist in IdM. New groups will be visible in SPM 5 to 20 minutes after they are created.
  • Group members can add other groups but cannot remove their own.

Edit the data in the ServiceProviderManager

After logging in, you will only see the ServiceProviders for which you have been authorized via a role or group.

Click the pencil icon in the "Edit" column to manage a ServiceProvider.

Screenshot of the SPM after logging in. Two additional columns are now displayed in the table after the Contact column: "Status" and "Edit."

You can edit the following:

Metadata

You can edit all the fields under Metadata, except:

  • Status
  • Federation
  • EntityId
  • EntityDescriptorID
  • Organization

These are specified by the IT Center. If the information is incorrect, please contact the IT-ServiceDesk.

To edit a field, click on the pencil icon next to it.

For more information about the fields, click on the blue “i” next to them.

Please note:
Changes will only be applied to the active IdP configuration after a manual approval process.

Screenshot of the Metadata tab, as described above.  It is the first of four tabs. The other tabs are: SPSSODescriptor, KeyDescriptor, and Organization.

SPSSODescriptor

Im Reiter SPSSODescriptor können Sie:

SPSSODescriptors

You can select the following SPSSODescriptors:

 Screenshot of the SPSSODescriptor tab (2/4). You can choose between "Use RequestsSigned?" and "Use AssertionsSigned?".

  • Request-Signed:
    • Verifies that the authentication request originates from the specified ServiceProvider.
    • To do so, configure a key descriptor certificate of the signing type. The certificate can be created as either signing and encryption or only signing (see KeyDescriptor).
  • Assertions-Signed:
    • The IdentityProvider signs the assertion with its private key (signature certificate), and the ServiceProvider uses the corresponding public key to verify the signature.
    • This ensures that the user data (username, roles, etc.) is trustworthy and has not been altered.
    • This setting is recommended.

AssertionConsumerService

The AssertionConsumerService must be filled out.

The URL is the endpoint to which the Identity Provider (IdP) sends the assertion containing the determined attributes. Without this information, logging in via Single-Sign On is not possible.

Screenshot of the SPSSODescriptors tab in the “AssertionConsumerService” section. You can enter the location, select the binding, and enter the index.

AttributeConsumingService

The AttributeConsumingService is optional.

It specifies the attributes required for logging in to the ServiceProvider.

Screenshot of the SPSSODescriptors tab in the “AttributeConsumingService” section. You can enter the ServiceName and RequestedAttribute.

KeyDescriptor (Certificate)

The SSL certificate securing the exchange between the IdentityProvider (IdP), RWTH, and the ServiceProvider is stored in the KeyDescriptor tab.

Please note:
To ensure a smooth transition, the old and new certificates should be configured in parallel for a period of time.

Screenshot of the KeyDescriptor tab (3/4). You can check the box if you want to use KeyDescriptor.

Click on I want to use KeyDescriptor and import a certificate. Then, click Apply Certificate.

Under "Applied Certificates," you can specify the purpose as encryption and/or signing.

Screenshot of the KeyDescriptor tab.  Checking "I want to use KeyDescriptor" will display the "Applied Certificates" and "New Certificates" sections. Under "New Certificates," you will find the "Select Certificate File" and "Apply Certificate" buttons.

For more information, see the topic Certificates on the DFN website.

Organization

In the Organization tab, you will find the following sections: Organization, Groups, and Contact Person.

Screenshot of the Organization tab (4/4), as described below.

Organization is added by the IT Center.

Under Groups, you can grant groups access to the SPM.

Under ContactPerson, you can add an administrative contact. Technical and content-related questions will be directed to this contact. 

Click on Add contact to database to add a contact person.

Please note:

  • At least one contact person must be added.
  • These entries are publicly visible.
  • Adding someone as a contact person does not grant them administrative rights or permissions.

Screenshot of the "Add contact to database" pop-up window. You can add the first name, last name, and email address. Below that are the "Save" and "Close" buttons.

    Attribute Overview

    After entering the metadata and clicking Save and Continue, the following page will appear:

    Screenshot of the Attribute Sharing page. The attributes are described below.

    The IT Center fills in the fields. The attribute display is for your reference only.

    AttributeFilterPolicy and PolicyRequirementRule

    The attributes "AttributeFilterPolicy" and "PolicyRequirementRule" are set up by the IT Center.

    SimpleAttributeRule

    Under "SimpleAttributeRule," you can specify which attributes must be sent to the ServiceProvider (ANY) and which are explicitly to exclude (NOT).

    Screenshot of the section “Simple AttributeRule” described above.

    AttributeRule with Filter

    Under "Attribute Rule with Filter", attributes are defined and filtered simultaneously according to their values based on the selected (regex) rules.

    All rules (AND), at least one rule (OR), or no rule (NOT) must be met.

    Screenshot of the section “AttributeRule with Filter” described above.

    Known Issues

    • Occasionally, you may need to click the pencil icon twice to start editing.
    • If two people edit the same ServiceProvider at the same time, the changes saved first will be applied. The other person's changes will be reset. For example:
      • Person A and Person B are working on the SP simultaneously.
      • Person B saves their changes first.
      • Person A's changes are reset. The SP reloads.
      • Person A is sent back to the beginning (Metadata) and receives the following message: "The Service Provider you were working on has been changed by someone else. The data has now been updated."
     

    last changed on 01/07/2026

    How did this content help you?

    Creative Commons Lizenzvertrag
    This work is licensed under a Creative Commons Attribution - Share Alike 3.0 Germany License