Skip to main content
Kinetic Community

SSO Plugin Authenticator

  1. Last updated
    10:49, 30 Mar 2016
  2. Save as PDF
SSO Plugin can be used as a single sign on solution to provide automatic login capabilities for Kinetic Request.

Feature

This external authenticator works with SSO Plugin (http://www.javasystemsolutions.com/jss/ssoplugin) from Java System Solutions.

 

Installation Files

Version Release Date Change
v03.00.00 2016-03-30
  • Handle forms that don't use external authentication.  NOTE - v3 requires Kinetic Request v5.2+.
v02.00.01 2015-05-13
  • Fixed issue using the wrong property names for the LookupARS features.
v02.00.00 2014-11-04
  • Added ability to lookup Remedy Login using a case insensitive search by the LookupARS.Case.Insensitive configuration property.  This version also drops support for the Remedy JNI API, so it requires Kinetic Request v5.1.1+.
v01.01.00 2013-12-12
  • Added the ability to exclude users from automatically authenticating if the user records belong to a specific Remedy Group.  The Remedy Group is configured with the ARS.UserForm.ExcludeByGroup.Name configuration property.
v01.00.06 2013-11-04
  • Verifies the Remedy user record is not disabled.  If the User record is disabled, the user will not be authenticated and will be directed to the page indicated the ARS.UserForm.DisabledUser.ErrorURL configuration property.
v01.00.05 2013-06-17
  • Added the ability to verify the user name detected by SSO Plugin exists in Remedy.  If not, the user will be directed to the authentication URL to login manually.
v01.00.04 2013-06-07
  • Added a manual login attribute to the session when the user authenticates manually from a login page.  This indicates to SSO Plugin that the user authenticated manually.
  • Cleaned up properties file and documentation.
v01.00.03 2013-04-30
  • Changed the AuthenticationURL default property value back to the default application login page.
v01.00.02 2012-12-12
  • Fixed a bug after authenticating the user that redirected the user back to a login page.
v01.00.01 2012-11-02
  • Added support for an AuthenticationURL configuration property if the user cannot be determined automatically.
v01.00.00 2012-06-07
  • Initial release
 
 

Installation Instructions

  1. SSO Plugin MUST be installed and setup before this authenticator will work.  Please consult the documentation  (http://www.javasystemsolutions.com/jss/ssoplugin) for SSO Plugin first.
  2. Unzip the archive file
  3. Copy the JSSAuthenticator.jar file to the Kinetic Request WEB-INF/lib directory.
  4. Copy the JSSAuthenticator.properties file to the Kinetic Request WEB-INF/classes directory.
  5. Login to the Kinetic Request AdminConsole and set the following properties:
    1. SSO Adapter Class => com.kd.kineticSurvey.authentication.JSSAuthenticator
    2. SSO Adapter Properties => C:\full\path\to\tomcat\webapps\kinetic\WEB-INF\classes\JSSAuthenticator.properties
    3. API Impersonate User => true   (**NOTE** - this setting may not be available on all versions of Kinetic Request, and will be determined automatically if it does not exist as a configurable property)
  6. Save the AdminConsole properties
  7. Restart the Web Server

 

Usage Instructions

Service items will use the SSO Adapter if they are set to require external authentication.  Service items don't always need to require authentication, so in Kinetic Request you will need to specify which service items do require external authentication.

  1. Using either the Remedy User Windows application or the Mid-Tier web application, open the Kinetic Request - Service Catalog Console form.
  2. Select a service item that will require authentication.
  3. Click on the Audit tab.
  4. Click the Require Authentication checkbox.
  5. Change the Authentication Type to External.
  6. Save the service item.
  7. Repeat steps 2 - 6 for each service item that will require authentication.

 

** NOTE - Some versions of Kinetic Request require the Authentication URL field to contain a value.  This SSO adapter does not use this field value, so any value entered here will be ignored.  Just enter any value (even a space will do) to satisfy the active link requirement that the field contains a value.