You have created a keystore view named SAML2 and generated at least one key-pair certificate for digital signatures and encryption.
For more information, see Using the AS Java Key Storage .
Use this procedure to enable Security Assertion Markup Language (SAML) 2.0 support and make the basic configurations for a SAML 2.0 service provider. This procedure only covers the first steps for preparing your SAP NetWeaver Application Server (AS) Java to operate as a SAML service provider.
If you have never configured your system for SAML 2.0, the system displays the following message:
System not configured to support SAML 2.0.
Select the keystore view and the key pairs your created for the provider.
Determine whether you want to include the public-key certificate in any digital signatures.
If you are using a public-key infrastructure for your SAML network or if the trusted providers otherwise require the inclusion of certificates to verify digital signatures, include the certificate.
If you are using self-signed certificates, do not include a certificate.
To provide a means for identity providers to validate the metadata of the service provider, sign the configuration metadata of the service provider.
The SOAP binding for the single logout (SLO) service and all the types and bindings for the Manage NameID (MNI) Service are disabled by default. Enabling any of these configurations for SLO and MNI without using them slows down the general performance.
This procedure only covers the initial basic configuration for enabling SAML 2.0 service provider. Once the service provider is enabled, you can modify the bindings and types supported by the service provider, trust a service provider, configure identity federation, and protect resources with SAML. For more information, see Configuring the AS Java as a Service Provider .