Page Comparison

...

You can configure the following for inbound authentication.

Configuring SAML2 web single-sign-on

...

...

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

...

...

...

The following table provides the list of digest algorithms available and their respective URI.

...

<SSOService>
...
	<UseAuthenticatedUserDomainCrypto>true<UseAuthenticatedUserDomainCrypto>
</SSOService>

...

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.
   Image Removed
3. Click Add. The following information is added for your service provider.
   Image Removed
   
   • 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.
   Image Removed
   • 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.
   Image Removed 

...

Configuring WS-Federation (Passive) or OpenID

1. Expand the WS-Federation (Passive) Configuration or 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. For WS-Federation (Passive), you can also specify the endpoint of the realm in Passive STS WReply URL.

   Tip

   Tip: When WS-Federation Passive request comes from a relying party, it checks whether there is a Passive STS WReply URL defined for the service provider. If there is a Passive STS WReply URL defined, it sets the replyTo URL as the one given in service provider configurations (this may override the replyTo parameter given in the request). If there is no Passive STS WReply URL defined in the service provider configuration, the replyTo URL given in the request is used. If there is no replyTo URL given in the request, wtrealm is used for as the replyTo URL.

Configuring Kerberos KDC

Kerberos is an authentication protocol which can be used to secure communications in web services. Kerberos enables you to exchange user credentials securely. Thus, it also provides mutual authentication in which the server can also authenticate itself to the client.

The Kerberos protocol uses a trusted third party called “Key Distribution Center” (KDC). KDC consists of two logical parts. They are:

• Authentication Server
• Ticket Granting Server

The actual user credentials are stored within the Authentication Server. The communicating parties will retrieve a Kerberos ticket from the Ticket Granting Server. TGS validates the ticket-requesting users' credentials with the Authentication Server.

Kerberos Security within WSO2 Identity Server

WSO2 Identity Server uses an ApacheDS-based LDAP server user store. It also has an ApacheDS based on KDC implementation. Users can use WSO2 Identity Server as a KDC and implement Kerberos security to secure communications between services and clients.
Enable KDC within WSO2 Identity Server.

To use KDC in Identity Server, you need to use the embedded LDAP which ships with WSO2 Identity Server. Thus, by default, the KDC server is disabled. To enable the KDC server, go to the Identity Server home directory and navigate to the <PRODUCT_HOME>/repository/conf folder. There you will find a file named embedded-ldap.xml. Open embedded-ldap.xml and find the <KDCServer/> XML tag. You will configure the XML element named enabled. Set its value to true. After modifying it, the XML configuration should look like this:

<KDCServer>
<Property name="name">defaultKDC</Property>
<Property name="enabled">true</Property>
<Property name="protocol">UDP</Property>
<Property name="host">localhost</Property>
<Property name="port">${Ports.EmbeddedLDAP.KDCServerPort}</Property>
<Property name="maximumTicketLifeTime">8640000</Property>
<Property name="maximumRenewableLifeTime">604800000</Property>
<Property name="preAuthenticationTimeStampEnabled">true</Property>
</KDCServer>

Service Principals

The KDC Server issues tickets to access a particular service. Thus, each type of service is associated with a particular service name. In the case of Kerbero, we call the service name “Service Principal Name” (SPN). Before we assign an SPN to a service, we need to define the “Service Principal Name” in KDC.

Users can use this screen to perform operations on service principals.

...

• Service Principal Name – Name of the service principal. This usually takes following format: <Service Name>/<Host where service is running>. This field is mandatory.
• Password – The password given to the service principal. You would use this password in the appropriate service's rampart configuration. Thus, the appropriate service will provide a password, given in rampart configuration, to KDC when it needs to authenticate itself to KDC. This field is mandatory.
• Re-Type Password – Re-type password provided in the "Password" section to make sure the given password is accurate. This field is mandatory.
• Description – Brief description of the service principal. This field is not mandatory.
  Image Removed

...