2016-10-03 16 views
0

在對同一版本服務器運行Worklight Admin命令行工具版本6.3.0.00.20141127-1357時,我收到錯誤消息。運行「list apps」命令和其他一些特定於應用程序的查詢時會發生這種情況。關鍵'deviceProvisioningRealm'的llegal JSON值:運行時爲空wladm

/app/IBM/MobileFirst_Platform_Server/shortcuts/wladm --configfile=/app/IBM/bldsrvwladmconfig.txt 

錯誤訪問 http://localhost:9080/worklightadmin/management-apis/1.0/runtimes/worklight/applications?pageSize=1000000000&locale=en_US: HTTP/1.1 500內部服務器錯誤FWLSE3000E:服務器誤差檢測 。鍵'deviceProvisioningRealm'的非法JSON值:空

獲取URL的內容直接成功返回數據。

APAR PI33197引用了類似的錯誤,但未解釋原因或解決方案。

authenticationConfig.xml:

 <?xml version="1.0" encoding="UTF-8"?> 
    <tns:loginConfiguration xmlns:tns="http://www.worklight.com/auth/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
    <!-- Licensed Materials - Property of IBM 5725-G92 (C) Copyright IBM Corp. 
       2006, 2013. All Rights Reserved. US Government Users Restricted Rights - 
       Use, duplication or disclosure restricted by GSA ADP Schedule Contract with 
       IBM Corp. --> 
     <staticResources> 
      <resource id="subscribeServlet" securityTest="SubscribeServlet"> 
          <urlPatterns>/subscribeSMS*;/receiveSMS*;/ussd*</urlPatterns> 
        </resource> 
     </staticResources> 
     <securityTests> 
      <customSecurityTest name="SubscribeServlet"> 
       <test realm="wl_directUpdateRealm" step="1"/> 
       <test isInternalUserID="true" realm="SubscribeServlet"/> 
      </customSecurityTest> 
      <customSecurityTest name="ISAMforWorklight-web-securityTest"> 
        <test realm="wl_antiXSRFRealm" /> 
        <test realm="WASLTPARealm" isInternalUserID="true" step="1"/> 
      </customSecurityTest> 
      <customSecurityTest name="ISAMforWorklight-Step-up-securityTest"> 
       <test realm="wl_directUpdateRealm" step="1"/> 
       <test isInternalDeviceID="false" isInternalUserID="true" realm="WASLTPARealm"/> 
     </customSecurityTest> 
     </securityTests> 
     <realms> 
      <realm loginModule="WASLTPAModule" name="WASLTPARealm"> 
        <className>com.worklight.core.auth.ext.WebSphereFormBasedAuthenticator</className> 
        <parameter name="login-page" value="/login.html"/> 
        <parameter name="error-page" value="/loginError.html"/> 
      </realm> 
      <realm loginModule="rejectAll" name="SubscribeServlet"> 
       <className>com.worklight.core.auth.ext.HeaderAuthenticator</className> 
      </realm> 
      <realm name="WorklightConsole" loginModule="requireLogin"> 
        <className>com.worklight.core.auth.ext.FormBasedAuthenticator</className> 
        <onLoginUrl>/console</onLoginUrl> 
      </realm> 
      <realm name="deviceProvisioningRealm" loginModule="rejectAll"> 
        <className>com.worklight.core.auth.ext.HeaderAuthenticator</className> 
      </realm> 
     </realms> 
     <loginModules> 
      <loginModule name="rejectAll"> 
       <className>com.worklight.core.auth.ext.RejectingLoginModule</className> 
      </loginModule> 
      <loginModule name="WASLTPAModule"> 
          <className>com.worklight.core.auth.ext.WebSphereLoginModule</className> 
        </loginModule> 
     </loginModules> 
    </tns:loginConfiguration> 

回答

0

此APAR已被固定在6.3.0.00.20150305-1844版本。請下載Fix Central.的最新修補程序我們的修補程序是累積的,因此最新的修補程序將包含此APAR的修補程序。

+0

APAR提到編輯authenticationConfig.xml解決了這個問題。我可以找出該決議的細節嗎? –

+0

如果您上傳authenticationConfig.xml,我們可以幫助您查看和建議。這可能包含一些敏感信息,所以最好提交PMR,我們可以幫助您。我可以問你爲什麼不能安裝最新的修復程序? – TyLy

+0

安裝最新的修補程序需要在所有環境中的20多個運行時間完成,QA迴歸週期等。這只是一個不小的努力。將上傳一個已清理的authconfig。 –