This documentation is for WSO2 Identity Server 5.0.0. View documentation for the latest release.
Configuring Inbound Authentication for a Service Provider - Identity Server 5.0.0 - WSO2 Documentation
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

You can configure the following in inbound authentication.

Configuring Inbound Authentication

Configuring SAML2 web single-sign-on

  1. Expand the SAML2 Web SSO Configuration and click Configure.
  2. Fill in the form that appears.
     
  3. Click Register.

The following points should be taken into consideration when filling the above New Service Provider form.

  • Specify the Issuer. Note that this should be equal to the ServiceProviderID value mentioned in the authenticators.xml of the relying party Carbon server.

  • Specify the Assertion Consumer URL. This is the URL to which the browser should be redirected after the authentication is successful. It should have this format: https://(host-name):(port)/acs.

  • Specify the NameID format.
  • Select Use fully qualified username in the NameID if that feature is required.

  • Select Enable Response Signing to sign the SAML2 Responses returned after the authentication.
  • Select Enable Assertion Signing to sign the SAML2 Assertions returned after the authentication. SAML2 relying party components expect these assertions to be signed by the Identity Server.

  • Select Enable Signature Validation in Authentication Requests and Logout Requests if you need this feature configured.

  • Enable Assertion Encryption, if you wish to encrypt the assertion.
  • Select the Certificate Alias from the dropdown. This is the Identity Server tenant's public certificate.
  • Select Enable Single Logout so that all sessions are terminated once the user signs out from one server. You can enter a Custom Logout URL if required.

  • Select Enable Attribute Profile to enable this and add a claim by entering the claim link and clicking the Add Claim button.

  • Select Enable Audience Restriction to restrict the audience. You may add audience members using the Audience text box and clicking the Add Audience button.

  • Select the Enable IdP Initiated SSO checkbox to enable this feature.

Configuring OAuth/OpenID Connect

OAuth provides a method for clients to access server resources on behalf of a resource owner (such as a different client or an end-user). It also provides a process for end-users to authorize third-party access to their server resources without sharing their credentials (typically, a username and password pair), using user-agent redirections.

OpenID Connect is a simple identity layer on top of the OAuth 2.0 protocol. It allows Clients to verify the identity of the End-User based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the End-User in an interoperable and REST-like manner.

OpenID Connect allows clients of all types, including Web-based, mobile, and JavaScript clients, to request and receive information about authenticated sessions and end-users. The specification suite is extensible, allowing participants to use optional features such as encryption of identity data, discovery of OpenID Providers, and session management, when it makes sense for them.

To enable OAuth support for your client application, you must first register your application by providing an application name and a callback URL. Follow the instructions below to add a new application.

  1. Expand the OAuth/OpenID Connect Configuration and click Configure.
  2. Fill in the form that appears. For the Allowed Grant Types you can disable the ones you do not require or wish to block.
  3. Click Add. The following information is added for your service provider.

    • OAuth Client Key - This is the client key of the service provider, which will be checked for authentication by the Identity Server before providing the access token.
    • OAuth Client Secret - This is the client secret of the service provider, which will be checked for authentication by the Identity Server before providing the access token. Click the Show button to view the exact value of this.

When filling out the New Application form, the following should be taken into consideration.

  • Selecting OAuth Version as 1.0a removes all the configurable Allowed Grant Types. This is because this version of OAuth does not support grant types.
  • The Callback Url is the exact location in the service provider's application where an access token would be sent. This is a required field and important to configure as it is imperative that the service provider receives the access token. This is necessary for security purposes to ensure that the token is not compromised.
  • The following are the grant types that are used to get the access token.
    • Code - Entering the user name and password required at the service provider will result in a code being generated. This code can be used to obtain the access token.
    • Implicit - This is similar to the code grant type, but instead of generating a code, this directly provides the access token.
    • Password - This authenticates the user using the password provided and the access token is provided.
    • Client Credential - This is the grant type for the client key and client secret. If these two items are provided correctly by the service provider, the access token is sent.
    • Refresh Token - This will enable the user to obtain an access token by using the refresh token once the originally provided access token is used up.
    • SAML - This uses SAML as the grant type to obtain the access token.
    • IWA-NTLM - This is similar to the password grant type, but it is specific to Microsoft Windows users.

Configuring WS-Trust Security Token Service

This requires registration of relying party endpoint addresses and their corresponding public certificates. In this scenario, STS generates a symmetric key and encrypts it with the public key of the relying party. This is included in the subject confirmation section of the SAML token, which is validated at the relying party end.

Follow the instructions below to configure STS for obtaining tokens.

  1. Expand the WS-Trust Security Token Service Configuration and click Configure.
  2. Specify the required information in the form that appears.
    • Endpoint Address - Relying party service endpoint where the token is being delivered to. This is a required field.
    • Certificate Alias - Corresponding public certificate for the service endpoint.
  3. Click Apply. The following information is added to your service provider.
     

Configuring WS-Federation (Passive) and OpenID

  1. Expand the WS-Federation (Passive) Configuration and OpenID Configuration.
  2. Enter the identifier for the Passive STS Realm and the OpenID Realm. These identifiers need to be specified as identification when the service provider reaches out to the Identity Server.
  • No labels