Service providers (SP) can be managed from Authentication > SAML IdP > Service Providers.
- Select Create New.
- Enter the following information:
IdP address To configure the IdP address (and IdP settings below), you must have already configured the server's address under Authentication > SAML IdP > General. SP name Enter a name for the SP. IdP prefix
Select a prefix for the IdP that is appended to the end of the IdP URLs.
Select + to create an alternate IdP prefix. Alternatively, you can select Generate prefix in the Create Alternate IdP Prefix dialog to generate a random 16 digit alphanumeric string.
Select x to remove the IdP prefix.
IdP entity id
The IdP's entity ID, for example:
IdP single sign-on URL
The IdP's login URL, for example:
IdP single logout URL
The IdP's logout URL, for example:
Select a server certificate to use for the SP. If a certificate is not selected, the specified default IdP certificate is used.
IdP signing algorithm
Select an IdP signing algorithm from the dropdown.
Support IdP-initiated assertion response
Allows the IdP to send an assertion response to the SP without a prior request from the SP.
Enabling this setting allows the SP to participate in IdP initiated login, and causes the SP to appear in the IdP login portal.
Allows SP to redirect user to the provided URL after a successful assertion response.
Participate in single logout
Enable or disable participation in single logout for the SAML IdP service.
SP Metadata SP Metadata fields are only available once the SAML Service Provider settings has been saved. SP entity id Enter the SP's entity ID. SP ACS (login) URL
Enter the SP's Assertion Consumer Service (ACS) login URL.
Click Alternative ACS URLs to configure up to three additional ACS (login) and SLS (logout) URLs.
SP SLS (logout) URL Enter the SP's Single Logout Service (SLS) logout URL. SAML request must be signed by SP Enable this option and import the SP certificate for authentication request signing by the SP.
SP certificate: The SP request is signed by the specified certificate.
Direct CA certificate: The SP request must contain the SP certificate fingerprint that was used to sign the request, and the certificate fingerprint must be issued by the CA specified in the configuration.
The primary certificate for verifying the SP request signature.
Displays the detected fingerprint algorithm of the certificate fingerprint or alternative certificate fingerprint.
Alternative certificate fingerprint
Specify a second acceptable certificate for verifying the SP request signature. FortiAuthenticator will accept SP requests with a valid signature from either configured certificate.
Use ACS URL from SP authentication request
When enabled, indicates that the ACS URL must be included within the SP request, and that the FortiAuthenticator must use it instead of the pre-configured ACS URL.
Authentication Authentication method
Select one of the following:
Mandatory password and OTP
Every configured password and OTP factors
Password and FIDO
Enable this option if you would like to have certain users bypass the OTP verification, so long as they belong to a trusted subnet.
Select Configure subnets to configure trusted subnets (under Authentication > User Account Policies > Trusted Subnets).
Select All trusted subnets to add all the available trusted subnets.
You can specify the trusted subnets by selecting Specify trusted subnets and clicking the pen icon. This opens a window where you can choose from a list of available trusted subnets.
This option is only available for Mandatory password and OTP and Every configured password and OTP factors authentication methods.
Application name for FTM push notification
Enter the client application name. This field is displayed on the FortiToken app.
When creating a new SP or upgrading to FortiAuthenticator 6.4, the SP name is the default client application name.
Use FIDO-only authentication if requested by the SP
Enable to use FIDO-only authentication if requested by the SP.
This option is not available for FIDO-only and Password and FIDO authentication methods.
Assertion Attributes Subject NameID
Select the user attribute that serves as SAML assertion subject NameID.
Select from either Username, Email, Remote LDAP user DN, Remote LDAP user objectGUID, Remote LDAP user mS-DS ConsistencyGuid, Remote LDAP Custom attribute, Remote SAML Subject NameID, or Remote SAML Custom assertion.
If the attribute selected is not available for a user, Username is used by default.
Format Select from Unspecified, Transient, or Persistent.
Include realm name in subject NameID
When enabled, you can select the username/realm format to include in subject NameID.
Select Create New to create a new attribute that is added to SAML assertion.
The following user attributes are available when creating a new assertion attribute:
IAM account name
IAM account alias
Remote LDAP server:
- Custom attribute (supports multiple values)
Remote RADIUS server:
When RADIUS attribute is selected as the User attribute, the following additional settings are available in the Create New Assertion Attribute dialog:
Vendor: The RADIUS vendor name.
Attribute ID: The attribute within the vendor's RADIUS dictionary.
Remote SAML server:
SAML group membership
Realm (returns the realm that the end user was authenticated against)
Debugging Options Do not return to service provider automatically after successful authentication, wait for user input Enable this option to let users choose where to navigate to after they are authenticated. Disable this service provider Disables the SP.