混合 Android 应用程序未连接到 MobileFirst 服务器

Question

在我的 QA 环境中，混合 Android 应用未连接到 MFP 服务器。
在我的本地计算机上，使用 MFP CLI 工具，应用程序连接没有问题。
在我的 QA 环境中，混合 iPhone 应用程序连接到 MFP 服务器。

失败的WL.Client.connect() 上的回调得到这个错误对象：

{
  "status": 403
}

这是来自错误处理程序的堆栈跟踪：

08-25 14:31:56.016: D/CordovaLog(27971): file:///android_asset/www/default/assets/js/dependencies.js: Line 23 : trace: Error
08-25 14:31:56.016: D/CordovaLog(27971):     at Object.connectionFailure [as onFailure] (file:///android_asset/www/default/assets/js/dependencies.js:23:190)
08-25 14:31:56.016: D/CordovaLog(27971):     at onFailureResetSettings (file:///android_asset/www/default/worklight/worklight.js:8251:12)
08-25 14:31:56.016: D/CordovaLog(27971):     at onInitFailure (file:///android_asset/www/default/worklight/worklight.js:8245:4)
08-25 14:31:56.016: D/CordovaLog(27971):     at Object.onFailure (file:///android_asset/www/default/worklight/worklight.js:951:20)
08-25 14:31:56.016: D/CordovaLog(27971):     at klass.window.WLJSX.Ajax.WLRequest.WLJSX.Class.create.onFailure (file:///android_asset/www/default/worklight/worklight.js:3650:26)
08-25 14:31:56.016: D/CordovaLog(27971):     at klass.window.WLJSX.Ajax.WLRequest.WLJSX.Class.create.onWlFailure (file:///android_asset/www/default/worklight/worklight.js:3599:12)
08-25 14:31:56.016: D/CordovaLog(27971):     at Object.<anonymous> (file:///android_asset/www/default/worklight/worklight.js:3437:27)
08-25 14:31:56.016: D/CordovaLog(27971):     at Object.<anonymous> (file:///android_asset/www/default/worklight/wljq.js:1202:33)
08-25 14:31:56.016: D/CordovaLog(27971):     at fire (file:///android_asset/www/default/worklight/wljq.js:1047:30)
08-25 14:31:56.016: D/CordovaLog(27971):     at Object.self.fireWith [as rejectWith] (file:///android_asset/www/default/worklight/wljq.js:1158:7)

我在服务器日志中没有看到任何关于被拒绝的连接请求的信息。

我从我的WL.Client.init() 调用的成功处理程序调用WL.Client.connect()，它本身在窗口加载事件中被调用。

（注意：基于下面的 cmets，我已更改为从 wlCommonInit() 调用 connect()，但没有任何变化......上面的堆栈跟踪来自该场景）

这是连接的代码：

(function () {
  'use strict';

  angular
    .module('myng-worklight', [])
    .run(WorklightRun)

  WorklightRun.$inject = ['$rootScope', '$q'];

  /**
  * Load worklight
  */
  function WorklightRun($rootScope, $q) {

    // Worklight statuss
    var worklightDeferred = $q.defer();
    $rootScope.worklightPromise = worklightDeferred.promise;
    $rootScope.worklightLoaded = false;
    $rootScope.worklightConnected = false;

    var worklightLoadEvent = null;
    worklightLoadEvent = document.createEvent('CustomEvent');

    // Worklight connect options
    var wlConnectOptions = {
      timeout: 30000,

      onFailure: connectionFailure,

      onSuccess: function () {
        console.log('MFP: Connected');
        $rootScope.worklightConnected = true;
        worklightDeferred.resolve();
      }
    };

    // Worklight init options
    var wlInitOptions = {
      timeout: 10000,

      onConnectionFailure: connectionFailure,

      onFailure: connectionFailure,

      onSuccess: function () {
        console.log('MFP: Loaded');
        $rootScope.worklightLoaded = true;
        if (window.addEventListener) {
          window.addEventListener(WL.Events.WORKLIGHT_IS_CONNECTED, wlConnectedHandler, true);
          window.addEventListener(WL.Events.WORKLIGHT_IS_DISCONNECTED, wlDisconnectedHandler, true);
        } else if (window.attachEvent) {
          window.attachEvent(WL.Events.WORKLIGHT_IS_CONNECTED, wlConnectedHandler);
          window.attachEvent(WL.Events.WORKLIGHT_IS_DISCONNECTED, wlDisconnectedHandler);
        }
        console.log('MFP: About to connect with: ' + JSON.stringify(wlConnectOptions, null, 2));
        WL.Client.connect(wlConnectOptions);
      }
    };
    // we should connect on the cb from init -- output!

    // Listen for load / onload and start worklight init
    if (window.addEventListener) {
      window.addEventListener('load', loadHandler, false);
    } else if (window.attachEvent) {
      window.attachEvent('onload', loadHandler);
    }


    function connectionFailure(err) {
      console.log('MFP: No Connection - ' + JSON.stringify(err, null, 2));
      worklightDeferred.reject(err);
    }

    function loadHandler() {
      try {
        console.log('MFP: Load event detected, about to init with: ' + JSON.stringify(wlInitOptions, null, 2));
        WL.Client.init(wlInitOptions);
      } catch (err) {
        console.error('MFP: "WL" not defined - ' + err);
        connectionFailure();
        worklightLoadEvent.initCustomEvent('worklightLoadFailure', true, false, {});
        window.dispatchEvent(worklightLoadEvent);
      }
    }

    function wlConnectedHandler() {
      $rootScope.worklightConnected = true;
      WL.App.hideSplashScreen();
    }

    function wlDisconnectedHandler() {
      $rootScope.worklightFailureAcknowledged = true;
      $rootScope.worklightConnected = false;
      WL.App.hideSplashScreen();
    }
  }
})();

这可能与 Android 应用的真实性设置有关？ （例如 application-descriptor.xml 中的 publicSigningKey 或 authenticationConfig.xml 中的 customTests）

这是来自application-descriptor.xml的相关位：

<android securityTest="customTests" version="1.0">
    <worklightSettings include="false"/>
    <pushSender key="XYZ" senderId="123"/>
    <security>
        <encryptWebResources enabled="false"/>
        <testWebResourcesChecksum enabled="false" ignoreFileExtensions="png, jpg, jpeg, gif, mp4, mp3"/>
        <publicSigningKey>MIIBI...</publicSigningKey>
        <packageName>com.MyPackage</packageName>
    </security>
</android>

来自authenticationConfig.xml：

<customSecurityTest name="customTests">
  <test realm="wl_antiXSRFRealm" step="1" />
  <test realm="wl_authenticityRealm" step="1" />
  <test realm="wl_remoteDisableRealm" step="1" />
  <test realm="wl_directUpdateRealm" mode="perSession" step="1" />
  <test realm="wl_anonymousUserRealm" isInternalUserID="true" step="1" />
  <test realm="wl_deviceNoProvisioningRealm" isInternalDeviceID="true" step="2" />
</customSecurityTest>

Answer 1

IMO 这是错误的。

您不应以这种方式致电WL.Client.connect。
Worklight API 应该在 wlCommonInit() 函数内调用，该函数位于 common\main.js 文件中，而不是来自 common\initOptions.js 文件。

查看Developer Center 提供的各种示例应用程序。它们都不是以这种方式实现的......（样本适用于 7.1 而您使用的是 6.2 并不重要，因为概念是相同的）。

所有的 onSuccess 都不应该那样做；