Oracle OpenSSO Fedlet Configuration (Oracle OpenSSO 8.0 Update 2 Release Notes)

Oracle OpenSSO 8.0 Update 2 Release Notes

Oracle OpenSSO Fedlet Configuration

This section describes how to initially configure the Fedlet with a service provider application:

After you finish the initial configuration for the Fedlet, continue with any additional configuration you want to perform. Several considerations are:

If you modify the Fedlet sp.xml file, you must re-import this file into your identity provider.
If you make other Fedlet configuration changes on the service provider side, convey this information to the identity provider administrator, so that the required configuration changes can be made on the identity provider side.

To Configure the Java Fedlet

On the identity provider side, generate the XML metadata for the identity provider and save the metadata in a file named idp.xml.

For Oracle OpenSSO 8.0 Update 2, use exportmetadata.jsp. For example:
```
http://opensso-idp.example.com:8080/opensso/saml2/jsp/exportmetadata.jsp
```

On the service provider side, unzip the Fedlet ZIP file (if necessary).

Create the Fedlet home directory, which is the directory where the Fedlet reads its metadata, circle of trust, and configuration properties files.

The default location is the fedlet subdirectory under the home directory of the user running the Fedlet web container (indicated by the user.home JVM property). For example, if this home directory is /home/webservd, the Fedlet home directory is:
```
/home/webservd/fedlet
```
To change the Fedlet default home directory, set the value of the JVM run-time com.sun.identity.fedlet.home property to the desired location. For example:
```
-Dcom.sun.identity.fedlet.home=/export/fedlet/conf
```
The Fedlet then reads its metadata, circle of trust, and configuration files from the /export/fedlet/conf directory.

Copy the following files from the Java Fedlet java/conf directory to the Fedlet home directory:
- sp.xml-template
- sp-extended.xml-template
- idp-extended.xml-template
- fedlet.cot-template

In the Fedlet home directory, rename the files you copied and drop -template from each name.

In the files you copied and renamed in the Fedlet home directory, replace the tags as shown in the next table:

Tag	Replace With
`FEDLET_COT`	Name of the circle of trust (COT) of which the remote identity provider and the Java Fedlet service provider application are members.
`FEDLET_ENTITY_ID`	ID (name) of the Java Fedlet service provider application. For example: `fedletsp`
`FEDLET_PROTOCOL`	Protocol of the web container for the Java Fedlet service provider application (such as `fedlet.war`). For example: `https`
`FEDLET_HOST`	Host name of the web container for the Java Fedlet service provider application (such as `fedlet.war`). For example: `fedlet-host.example.com`
`FEDLET_PORT`	Port number of the web container for the Java Fedlet service provider application (such as `fedlet.war`). For example: `80`
`FEDLET_DEPLOY_URI`	URL of the Java Fedlet service provider application. For example: `http://fedletsp.example.com/myFedletApp`
`IDP_ENTITY_ID`	ID (name) of the remote identity provider. For example: `openssoidp`
Note: If the Fedlet service provider or identity provider entity ID contains a percent sign (%) or comma (,), you must escape the character before replacing it in the `fedlet.cot` file. For example, change ”%” to ”%25" and ”," to ”%2C”.

Copy the FedletConfiguration.properties file from the Java Fedlet java/conf directory to the Fedlet home directory.

Copy the identity provider standard metadata XML file (from Step 1) to the Fedlet home directory. This file must be named idp.xml.

Import the Java Fedlet XML metadata file (sp.xml) into the identity provider.

For Oracle OpenSSO 8.0 Update 2, use the Register Remote Service Provider work flow under Common Tasks in the OpenSSO 8.0 Administration Console to import the Java Fedlet service provider metadata and to add the Java Fedlet service provider to a circle of trust.

Next Steps

Depending on your requirements, continue with any additional configuration for the Java Fedlet.

To Configure the .NET Fedlet

On the identity provider side, generate the XML metadata for the identity provider and save the metadata in a file named idp.xml.

For Oracle OpenSSO 8.0 Update 2, use exportmetadata.jsp. For example:
```
http://opensso-idp.example.com:8080/opensso/saml2/jsp/exportmetadata.jsp
```

On the service provider side, unzip the Fedlet ZIP file (if necessary).

Copy the following files from the .NET Fedlet asp.net/conf folder to your application's App_Data folder:
- sp.xml-template
- sp-extended.xml-template
- idp-extended.xml-template
- fedlet.cot-template

In the App_Data folder, rename the files you copied and drop -template from each name.

In the files you copied and renamed in the App_Data folder, replace the tags as shown in the next table:

Tag	Replace With
`FEDLET_COT`	Name of the circle of trust (COT) of which the remote identity provider and the .NET Fedlet service provider application are members.
`FEDLET_ENTITY_ID`	ID (name) of the .NET Fedlet service provider application. For example: `fedletsp`
`FEDLET_DEPLOY_URI`	URL of the .NET Fedlet service provider application. For example: `http://fedletsp.example.com/myFedletApp`
`IDP_ENTITY_ID`	ID (name) of the remote identity provider. For example: `openssoidp`

Copy the identity provider standard metadata XML file (from Step 1) to your application's App_Data folder. This file must be named idp.xml.

Copy the Fedlet.dll and the Fedlet.dll.config files from the .NET Fedlet asp.net/bin folder to the application's bin folder.

Import the .NET Fedlet XML metadata file (sp.xml) into the identity provider.

For Oracle OpenSSO 8.0 Update 2, use the Register Remote Service Provider work flow under Common Tasks in the OpenSSO 8.0 Administration Console to import the .NET Fedlet service provider metadata and to add the .NET Fedlet service provider to a circle of trust.

Next Steps

Depending on your requirements, continue with any additional configuration for the .NET Fedlet.