[
https://issues.apache.org/jira/browse/GERONIMO-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhen Zhang updated GERONIMO-5662:
---------------------------------
Comment: was deleted
(was: when execute step 7 ,fail to deploy app at new server [email protected]
you will find this info in server log:
2010-11-08 17:16:12,531 ERROR [DeploymentPortlet] The application was not
deployed.
Unable to resolve reference "ConfigurationFactory"
in gbean
default/prop-file-realm-tester/1-default/car?J2EEApplication=null,j2eeType=WebModule,name=default/prop-file-realm-tester/1-default/car
to a gbean matching the pattern
[?name=test-prop-file-realm#org.apache.geronimo.security.jaas.ConfigurationFactory]
due to: No matches for referencePatterns:
[?name=test-prop-file-realm#org.apache.geronimo.security.jaas.ConfigurationFactory]
org.apache.geronimo.common.DeploymentException: Unable to resolve reference
"ConfigurationFactory"
in gbean
default/prop-file-realm-tester/1-default/car?J2EEApplication=null,j2eeType=WebModule,name=default/prop-file-realm-tester/1-default/car
to a gbean matching the pattern
[?name=test-prop-file-realm#org.apache.geronimo.security.jaas.ConfigurationFactory]
due to: No matches for referencePatterns:
[?name=test-prop-file-realm#org.apache.geronimo.security.jaas.ConfigurationFactory]
at
org.apache.geronimo.deployment.DeploymentContext.getConfigurationData(DeploymentContext.java:534)
at org.apache.geronimo.deployment.Deployer.install(Deployer.java:342)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:265)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872)
at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
at
org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
at
org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
at java.lang.Thread.run(Thread.java:619))
> j_security_check 404 not found against security realm authentication
> --------------------------------------------------------------------
>
> Key: GERONIMO-5662
> URL: https://issues.apache.org/jira/browse/GERONIMO-5662
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 3.0
> Environment: OS:Windows XP SP3
> Java Version: 1.6.0_20
> Server:Geronimo 3.0-SNAPSHOT
> Reporter: Zhen Zhang
> Assignee: viola.lu
> Priority: Minor
> Fix For: 3.0
>
> Attachments: after-ff.txt, before-ff.txt, G5662.patch,
> G5662_New.patch, ie.txt, VerifyReplaceDefaultSecurityRealm-SEC001.zip
>
>
> setps to recur:
> 1. start the Geronimo server, and then open the admin console.
> 2.In security realms portlet, click on "Add new security realm" link.
> 3.Select realm name and use "test-prop-file-realm" for realm-name, and then
> select Properties File Realm and click on "Next" button.
>
> 4.Enter Users File URI (var/security/users.properties) and Groups File URI (
> var/security/groups.properties) and click on "Next" button.
>
> 5.Click on "Skip Test and Deploy" button.
> 6. Check the realm named "test-prop-file-realm" should be listed in the
> security realms portlet.
> 7.Deploy geronimo-ldap-demo-1.1.war using plan file
> prop-file-realm-tester.xml and access the application at
> http://localhost:8080/prop-file-realm-test
> 8.Access "Protect" link to verify that the realm is functional.Input
> username:system, password: manager
> 9.Login page just refreshed, not redirect to /protect/hello.html success
> page. And click "login" again, got an 404 not found error. This problem
> exists on Firefox and chrome, fine on IE
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
