Skip to main content
Kofax

MarkView Authentication - New Authentication methods in Kofax Markview 9.1 and above troubleshooting and diagnostics

Summary

13639

Applies To

  • ERP System: Oracle
  • MarkView Version: 9.1 and Greater

Overview

  • Markview 9.1 has added enhanced authentication methods and support for external authentication systems. Markview 9.1 has also added the ability for users to log out and a configurable timeout functionality to log users out automatically when their sessions are inactive.
  • Supported Authentication methods are as follows:
    • Form based login page
    • Single Sign On login
  • Supported External Systems are as follows:
    • Oracle E-Business Suite authentication
    • Markview internal authentication
    • Oracle Internet Directory
    • Microsoft Active Directory
    • LDAP v3 server
  • Configuration instructions for authentication methods and systems can be found in the User Authentication section of the Markview System Administrator guide

Troubleshooting Authentication

  • If the login screen is not appearing or you are recieving a 404 page not found error
    • Check the preference AUTH_LOGIN_HTTP_URL to ensure the url is correct. As you can not log in you will need to use the following query on the backend:
      select preference_value
          from mv_system_preference
      where preference_id =
          (select preference_id
                  from mv_preference_definition
          where preference_name = 'AUTH_LOGIN_HTTP_URL');
    • If you need to update this value you will need to use the following query:
      update mv_system_preference
          set preference_value = '&Enter_Value'
      where preference_id =
          (select preference_id
              from mv_preference_definition
            where preference_name = 'AUTH_LOGIN_HTTP_URL');
      commit;
    • If you are using a siteminder solution for single sign on ensure you can reach the site minder page from the client machine
  • If no users can login
    • Ensure the WEBCLNT_SEC_AUTH_TYPE preference is set correctly for the system you are using. As you can not log in you will need to use the following query on the backend:
      select preference_value
          from mv_system_preference
      where preference_id =
              (select preference_id
                  from mv_preference_definition
                  where preference_name = 'WEBCLNT_SEC_AUTH_TYPE');
      commit;

      The possible values for this preference and their corresponding systems are as follows:
      • CUSTOM—Allows for custom validation. Requires code in MVW_Authenticate_Custom package
      • ERP—Authenticates against the Oracle E-Business Suite username and password.
      • MV—(default) Authenticates against the MarkView username and password.
      • MSAD—Authenticates against the Microsoft Active Directory username and password.
      • OID—Authenticates against the Oracle Internet Directory username and password.
      • LDAP—Authenticates against the General LDAP Server username and password.
      • PSE—(obsolete)Authenticates against the PeopleSoft Enterprise username and password.

If you need to update this preference you will need to use the following query:

update mv_system_preference
    set preference_value = '&Enter_Value'
where preference_id =
    (select preference_id
        from mv_preference_definition
    where preference_name = 'WEBCLNT_SEC_AUTH_TYPE');
commit;
Note - this preference can also be set at the user level. So if only one user is having login issues you may want to confirm the preference at the user level for that particular user.
  • Troubleshooting the connection between Markview and external systems
    • Ensure the values set in Markview Home -> Administration -> Authentication Configuration are set properly. There is a test button on each page, please note however this only tests the connection it does not test the authentication itself.
    • Ensure you can ping the server running the external system from the machine the markview application server
  • If all steps have been completed and the preferences are correct, enable debug logging per the steps in the logging section and review the log for errors.

Logging

  • Enable Authentication Logging
    • To enable debug logging set the Markview Preference USERMGMT_LOGGING_LEVEL to DEBUG. No restart is required.
  • Disable PL/SQL Servlet Logging
    • To disable debug logging set the Markview Preference USERMGMT_LOGGING_LEVEL to Off. No restart is required.
  • Log File name and Location
    • When debug logging is enabled, all authentication events are logged in the file usermgmt.log
    • The usermgmt.log file can be found in a MarkView log location which is dependent upon middle tier type. Please see the following article for the location

Keywords: SSO Single Sign On Authentication Markview 9.1

  • Was this article helpful?