Skip to main content
Kofax

Single Sign On ( SSO ) for MarkView

5021
Article # 303792 - Page views: 683

Summary

5021

MarkView Version 9.0 and earlier:
ERP System: All

  • MarkView versions prior to 9.1 do not come pre-integrated with any Single Sign On (SSO) solution.
  • These MarkView versions do have configurable callouts that can be leveraged to provide this integration, but this requires customization.
  • Customization of MarkView products to work with SSO products would require an engagement with the Kofax Professional Services Team.
  • For more information on SSO configuration, please contact your Kofax Business Development Manager or your Kofax Account Executive.

 

MarkView Version 9.1:
ERP System: Oracle

  • MarkView version 9.1 onwards supports Single Sign-On (SSO) using a general approach of parsing the user credentials out of the HTTP header or cookie.
  • The SSO feature should be enabled via MV_ENABLE_SINGLE_SIGN_ON preference (requires a restart of the MarkView application server).
  • Please refer to the MarkView 9.1 Administrator's Guide Volume 2 section Setting up Single Sign-On for more information regarding Single Sign-On (SSO) configuration.

 

MarkView will support both options and provide an ability to configure the sources of credentials (headers or cookies) via below preferences:

  • AUTH_SSO_USERNAME_HEADER_FIELD - The name of the request header that contains the username. It defaults to SM_USER, for compatibility with Siteminder.
  • AUTH_SSO_USER_CREDENTIALS_HEADER_FIELD - The name of the request header that contains the user credentials. If this is set to the default (SM_USER) MarkView ignores this header field. If set to any other value, MarkView uses that value as the header field that contains the password for the user.
  • AUTH_SSO_USERNAME_COOKIE_NAME - The name of the cookie that contains the username. It defaults to SM_USER, for compatibility with Siteminder.
  • AUTH_SSO_USER_CREDENTIALS_COOKIE_NAME - The name of the cookie that contains the user credentials. If this is set to the default (SM_USER) MarkView ignores this cookie. If set to any other value, MarkView uses that value as the cookie that contains the password for the user.
  • Please refer to the MarkView 9.1 Administrator's Guide Volume 1 for more details regarding the above preferences.
  • Was this article helpful?