Oracle OpenSSO 8.0 Update 2 Release Notes

ProcedureTo Configure the .NET Fedlet

  1. 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
  2. On the service provider side, unzip the Fedlet ZIP file (if necessary).

  3. 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

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

  5. 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

  6. 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.

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

  8. 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.