MarkView Oracle Integration - After installing Oracle Applications Technology 11i.ATG_PF.H.delta.6 (RUP6 patch); users cannot authenticate to log into MarkView.

Applies To

• ERP System: ( Oracle )
• MarkView Version: (Version prior to 5.10.10)

Behavior

• After installing Oracle Applications Technology 11i.ATG_PF.H.delta.6 (RUP6 patch), users cannot authenticate to log into MarkView.
  This affects MarkView systems that have been configured to authenticate against Oracle Applications (i.e. MarkView systems where the WEBCLNT_SEC_AUTH_TYPE

Known Causes

• This issue (identified as Defect 26612) has been corrected in MarkView Patchset 5.10.10. Information about this patchset and all 5.10.x patchsets is available here:
  https://na1.salesforce.com/articles/General/1055

Resolution

• For customers running MarkView 5.0, this issue can be addressed by updating the MVW_Authenticate_Custom package body as follows:
  Replace:

  l_auth_result := FND_WEB_SEC.VALIDATE_LOGIN (
  p_user => UserID,
  p_pwd => Password );

  
  With:

  MVOA_Apps_Util.OpenParseCursor (
      'begin ' ||
      ':AuthResult := FND_WEB_SEC.VALIDATE_LOGIN ( '||
      'p_user => :UserID, p_pwd => :Password );' ||
      ' end; '
      , mvoa_apps_util_string);
  MVOA_Apps_Util.BindVariable ('AuthResult',l_auth_result,256);
  MVOA_Apps_Util.BindVariable ('UserID', UserID);
  MVOA_Apps_Util.BindVariable ('Password', Password);
  MVOA_Apps_Util.ExecuteCursor ( mvoa_apps_util_string );
  MVOA_Apps_Util.VariableValue ('AuthResult',l_auth_result);
  MVOA_Apps_Util.CloseCursor;

  
  And Declare:

  mvoa_apps_util_string constant varchar2(32) :=
      chr(075)||chr(064)||chr(106)||chr(126)||
      chr(064)||chr(034)||chr(056)||chr(093)||
      chr(107)||chr(060)||chr(067)||chr(113)||
      chr(056)||chr(108)||chr(085)||chr(105)||
      chr(104)||chr(074)||chr(042)||chr(096)||
      chr(074)||chr(042)||chr(093)||chr(075)||
      chr(121)||chr(082)||chr(042)||chr(118)||
      chr(048)||chr(085)||chr(036)||chr(065);

  
  beneath:

  l_auth_result varchar2(256);

Note: The attached MVW_Authenticate_Custom.pck and MVW_Authenticate_Custom-modified.pck files show the MVW_Authenticate_Custom package body before and after the specified changes.

It is the recommended policy of Kofax, Inc. that all system changes be applied in the customer's test environment and tested thoroughly before being migrated to a production environment.

Any customers running a version of MarkView older than 5.0 must upgrade to MarkView 5.5 and apply the 5.10.x Patchsets up through 5.10.10.