部署新战争后应用程序的工作灯控制台无法正常工作

Posted 2023-02-26

【中文标题】部署新战争后应用程序的工作灯控制台无法正常工作

【英文标题】：worklight console for app not working after deploying new war

【发布时间】：2014-10-02 20:37:45

【问题描述】：

通过服务器配置工具部署新战争后出现此错误。我试图恢复到原来的战争错误仍然存​​在。

Tomcat 7.0.30 Worklight 服务器 6.1.0.2

   javax.servlet.ServletException: Worklight Console initialization failed.Logged Exception:     java.lang.RuntimeException: conf/authenticationConfig.xml contains duplicated realm named: wl_anonymousUserRealm
    com.worklight.core.auth.impl.AuthenticationFilter.verifyServletInitialized(AuthenticationFilter.java:317)
    com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:111)

xml 是默认构建的，我的领域是在 context.xml 中为服务器定义的。

    <!-- 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. -->  

<!-- Uncomment the next element to protect the worklight console and the first section in securityTests below. -->
 <staticResources>
<!-- <resource id="worklightConsole" securityTest="WorklightConsole">
        <urlPatterns>/console*</urlPatterns>
     </resource> 
    -->
    <resource id="subscribeServlet" securityTest="SubscribeServlet">
        <urlPatterns>/subscribeSMS*</urlPatterns>
    </resource>
</staticResources> 

在下面进行测试，也必须将元素添加到 application-descriptor.xml 中。 -->

 <securityTests>
    <!-- 
    <customSecurityTest name="WorklightConsole">
        <test realm="WorklightConsole" isInternalUserID="true"/>
    </customSecurityTest>

    <mobileSecurityTest name="mobileTests">
        <testAppAuthenticity/> 
        <testDeviceId provisioningType="none" />
        <testUser realm="myMobileLoginForm" />
    </mobileSecurityTest>

    <webSecurityTest name="webTests">
        <testUser realm="myWebLoginForm"/>
    </webSecurityTest>

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


    <customSecurityTest name="AgentSecurityTest">
        <test isInternalUserID="true" realm="FbitnAgentRealm"/>
    </customSecurityTest>

</securityTests> 

<realms>
    <!--realm name="ConsumerRealm" loginModule="AnonymousLoginModule" >
        <className>com.worklight.integration.auth.AdapterAuthenticator</className>
        <parameter name="login-function" value="ConsumerPolicy.onAuthRequired"/>
        <parameter name="logout-function" value="ConsumerPolicy.onLogout"/>
    </realm-->
    <realm loginModule="StrongDummy" name="SampleAppRealm">
        <className>com.worklight.core.auth.ext.FormBasedAuthenticator</className>
    </realm>

    <realm loginModule="requireLogin" name="WorklightConsole">
        <className>com.worklight.core.auth.ext.FormBasedAuthenticator</className>
        <onLoginUrl>/console</onLoginUrl>
    </realm>

    <realm loginModule="rejectAll" name="SubscribeServlet">
        <className>com.worklight.core.auth.ext.HeaderAuthenticator</className>          
    </realm>
    <!-- For websphere -->
    <!-- realm name="WASLTPARealm" loginModule="WASLTPAModule">
        <className>com.worklight.core.auth.ext.WebSphereFormBasedAuthenticator</className>
        <parameter name="login-page" value="/login.html"/>
        <parameter name="error-page" value="/loginError.html"/>
    </realm -->
    <realm name="FbitnAgentRealm" loginModule="FbitnAgentLogin">
        <className>com.fbitn.WorklightCustomAuthenticator</className>
    </realm>
</realms>

<loginModules>
    <loginModule name="FbitnAgentLogin">
        <className>com.fbitn.WorklightCustomLogin</className>
    </loginModule>
    <!--loginModule name="AnonymousLoginModule">
        <className>com.worklight.core.auth.ext.NonValidatingLoginModule</className>
    </loginModule-->

    <!--loginModule name="HeaderLoginModule" canBeResourceLogin="true" isIdentityAssociationKey="true" audit="true"-->

    <loginModule name="StrongDummy">
        <className>com.worklight.core.auth.ext.NonValidatingLoginModule</className>
    </loginModule>

    <loginModule name="requireLogin">
        <className>com.worklight.core.auth.ext.SingleIdentityLoginModule</className>
    </loginModule>

    <loginModule name="rejectAll">
        <className>com.worklight.core.auth.ext.RejectingLoginModule</className>
    </loginModule>

    <!-- For websphere -->
    <!-- loginModule name="WASLTPAModule">
        <className>com.worklight.core.auth.ext.WebSphereLoginModule</className>
    </loginModule -->

    <!-- For enabling SSO with no-provisioning device authentication -->
    <!-- <loginModule name="MySSO" ssoDeviceLoginModule="WLDeviceNoProvisioningLoginModule">
        <className>com.worklight.core.auth.ext.NonValidatingLoginModule</className>
    </loginModule> -->
    <!-- For enabling SSO with auto-provisioning device authentication -->
    <!-- <loginModule name="MySSO" ssoDeviceLoginModule="WLDeviceAutoProvisioningLoginModule">
        <className>com.worklight.core.auth.ext.NonValidatingLoginModule</className>
    </loginModule> -->
</loginModules>

【问题讨论】：

嗯...和这里一样 :/ -- ***.com/questions/25785067/…

@IdanAdar 是的，但没有人回答这个人。

是的，我的意思不是还没有答案。

我最近用修订包 2 更新了服务器，然后用修订包更新了我的工作室。建立了一场新的战争并且发生了这种情况，试图恢复到旧的战争并且它仍然发生。

我还不相信它与修订包有关，但与部署时服务器上的内容有关。在部署新的战争之前尝试清除现有的战争？

【参考方案1】：

服务器上有两个版本。 Tomcat/Worklight/app 和 Tomcat/webapps/app。我不确定服务器配置工具是否用于部署第一个，但用于第二次部署。我从 Worklight 文件夹中删除了应用程序内容，并将原始文件夹保留在 webapps 下，server.xml 配置为读取两个目录，只需要一个。

我发现这是因为 worklight-jee-library.jar 安装在 tomcat/lib 和 tomcat/Worklight/app 下。我相信在安装 Worklight 6.1 时，安装经理将 lib 中的那个放在了那里。

【讨论】：

谢谢。你介意分享你的解决方案吗@@***.com/questions/25785067/…