Oracle WebCenter Interaction Web Service Development Guide

     Previous Next  Open TOC in new window   View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Deploying a .NET Authentication Service

To deploy an authentication service to IIS and .NET, follow these instructions.


  • The Oracle WebCenter Interaction Development Kit (IDK) must be installed on the server to which you intend to deploy.
  • You must have implemented ISyncProvider and IGroup (for synchronization), IAuthProvider (for authentication), or both. For details, see Implementing an Authentication Service.

This topic describes how to deploy an Authentication Service implemented in Java to a Java application server.

To deploy an authentication service to IIS and .NET:
  1. Ensure that you have built your project with the AuthProviderSoapBinding.asmx and/or SyncProviderSoapBinding.asmx SOAP endpoints.

    If this service uses SCI, also include SCIProviderBinding.asmx. These files can be found in your IDK installation.

    The Oracle WebCenter Interaction Development Kit (IDK) installation is typically installed to C:\Program Files\plumtree\idk\<version>\devkit\

  2. Update Web.config for services that provide authentication.

    If this service provides authentication, add the following nodes to <appSettings>:


    • <add key="AuthProviderAssembly" value="assembly name" />

      Where assembly name is the name of the assembly containing your IAuthProvider implementation.

    • <add key="AuthProviderImpl" value="fully qualified path" />

      Where fully qualified path is the fully qualified path to the class implementing IAuthProvider.

    For example:

    <appSettings>
    
        <add key="AuthProviderAssembly" value="Helloworld" />
    
        <add key="AuthProviderImpl" value="Plumtree.Remote.Auth.Helloworld.Auth" />
    
    ...
  3. Update Web.config for services that provide synchronization.

    If this service provides synchronization, add the following nodes to <appSettings>:


    • <add key="SyncProviderAssembly" value="assembly name" />

      Where assembly name is the name of the assembly containing your ISyncProvider implementation.

    • <add key="SyncProviderImpl" value="fully qualified path" />

      Where fully qualified path is the fully qualified path to the class implementing ISyncProvider.

    For example:

    <appSettings>
    
    ...
    
        <add key="SyncProviderAssembly" value="Helloworld" />
    
        <add key="SyncProviderImpl" value="Plumtree.Remote.Auth.Helloworld.Sync" />
    
    ...
  4. Update Web.config for services that use SCI.

    If this service uses SCI, add the following nodes to <appSettings>:


    • <add key="AdminEditorAssembly" value="assembly name" />

      Where assembly name is the name of the assembly containing your IAdminEditor implementation.

    • <add key="AdminEditorImpl" value="fully qualified path" />

      Where fully qualified path is the fully qualified path to the class implementing IAdminEditor.


  Back to Top      Previous Next