Managing Trusted Identity Providers
[ Dorian: Administrators Guide | Developers Guide | Users Guide | caGrid: Documentation Guides ]
![]() |
| Managing Trusted Identity Providers |
- Auto Approval / Auto Renewal - A new user is automatically registered and given access to the grid. (user's status is active) When a user's whose long term certificate expires it is automatically renewed.
- Auto Approval / Manual Renewal - A new user is automatically registered and given access to the grid. (user's status is active) When a user's whose long term certificate expires, an administrator is required to manually renew it.
- Manual Approval / Auto Renewal - A new user is automatically registered but not granted access, and administrator is required to grant access. (user's status is pending) When a user's whose long term certificate expires it is automatically renewed.
- Manual Approval / Manual Renewal - A new user is automatically registered but not granted access, and administrator is required to grant access. (user's status is pending) When a user's whose long term certificate expires, an administrator is required to manually renew it.
When Dorian receives a SAML assertion from a Trusted IdP it verifies that the assertion was signed with the private key that corresponds to the Trusted IdP's certificate. Thus the Trusted IdP's certificate must be specified. Each Trusted IdP must be configured with a list of acceptable authentication methods. A SAML authentication assertion specifies the method in which the Trusted IdP authenticated the user. In order for the SAML assertion to be accepted by Dorian, the authentication method specified in the assertion must be specified as acceptable in the corresponding Trusted IdP. Dorian requires the SAML assertions provided by Identity Provider's to specify four attributes which are maintained by Dorian for each user, such that Dorian and its administrators may effectively administrate grid user accounts. These attributes include (1) user's local unique user id within the IdP, (2) user's first name, (3) user's last name, (4) user's email address. In a SAML Assertion attributes are specified with a namespace and name, because the naming of attributes may differ from IdP to IdP, Dorian does not place requirements on how the attributes are named within the SAML Assertion so long as the values of the attributes meet Dorian's formatting requirements. Therefore the namespace and name of each of the four attributes must be specified for each Trusted IdP, such that Dorian knows what to look for when it receives a SAML assertion from the IdP. To manage Trusted IdPs through the GAARDS UI, use the following steps.
- From the User Management menu select Grid Account Management => Trusted Identity Provider(s).
- The Trusted Identity Provider Management window opens (shown below). All the IdPs trusted by a Dorian can be listed as follows:
- From the Service drop down, select the service URI of the Dorian you wish to list the Trusted IdPs of, if it is not in the list enter it manually.
- From the Proxy drop down, select the proxy or credentials to use to authenticate to Dorian. This must be a proxy of a Dorian administrator.
- Click the Find Trusted Identity Providers button. The Trusted IdPs are listed in the table below the progress bar. The list includes the Trusted IdP's id, human readable name, and status. In the example below, there are two Trusted IdPs listed; the first is Dorian's Local IdP and the second is the Ohio State University IdP. Thus in the example below, Dorian would accept credentials from its local IdP and from the Ohio State University.
Adding a Trusted Identity Provider
![]() |
| Adding a Trusted Identity Provider |
- Click the Add Trusted IdP button from the Trusted Identity Provider ManagementAdd Trusted IdP window to open the window (shown below) which consists of three tabs, each of which requires the information to be specified.
- IdP Information Tab - specify the name, status, user policy, and acceptable authentication methods.
- Certificate Tab - specify the certificate that corresponds to the private key that is used by the IdP in signing SAML Assertions that is issues. The certificate must be specified in PEM format; click the Import Certificate button to open a file browser in which you may browse to the certificate.
- Attributes Tab - specify the namespace and name that the IdP uses for representing each of the four required attributes in its SAML assertions, such that Dorian knows how to retrieve the attributes from the IdP's SAML assertions.
- Once you have specified all the required information, click the Add button to add the IdP to Dorian as a Trusted IdP. Assuming you set the status of the newly added IdP to active, Dorian immediately begins accepting SAML assertions from the IdP.
Viewing/Updating a Trusted Identity Provider
To view/update a Trusted IdP, use the following steps.
- Select the Trusted IdP of interest and click the View/Edit Trusted IdP button from the Trusted Identity Provider Management window to open the Trusted IdP window. The Trusted IdP window consists of three tabs:
- IdP Information Tab - update the name, status, user policy, and acceptable authentication methods.
- Certificate Tab - update the certificate that corresponds to the private key that is used by the IdP in signing SAML Assertions that is issues. If you update the certificate it must be specified in PEM format; click the Import Certificate button to open a file browser in which you may browse to the certificate.
- Attributes Tab - update the namespace and name that the IdP uses for representing each of the four required attributes in its SAML assertions.
- Once you have finished updating the Trusted IdP's information click the Update button to commit the changes, which take effect immediately.
Removing a Trusted Identity Provider
To remove a Trusted IdP, select the Trusted IdP to remove from the Trusted Identity Provider Management window and click the Remove Trusted IdP button. Removing a Trusted IdP will remove all user accounts associated with the IdP, revoking access to all users associated with the IdP.







