[jira] Commented: (GERONIMO-314) JACC (JSR 115) authorization from Tomcat Web Container
[ http://issues.apache.org/jira/browse/GERONIMO-314?page=comments#action_57857 ] Jeff Genender commented on GERONIMO-314: JACC TomcatGeronimoRealm module added that implements JACC for Tomcat. This has been committed for me by Alan. This module still requires the deployer/builder updates to set the object from the descriptors. > JACC (JSR 115) authorization from Tomcat Web Container > -- > > Key: GERONIMO-314 > URL: http://issues.apache.org/jira/browse/GERONIMO-314 > Project: Apache Geronimo > Type: Task > Components: web, security, Tomcat > Reporter: David Blevins > Assignee: Alan Cabrera > > At current time any JACC (JSR 115) providers configured with Geronimo are not > leveraged by the Geronimo/Tomcat integration as is required by the J2EE 1.4 > (JSR 151) specification. Security constraints are handled internally by > Tomcat and not integrated with Geronimo. > Java Authorization Contract for Containers (JACC) > JSR 115 - http://www.jcp.org/en/jsr/detail?id=115 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-313) JAAS Login from Tomcat Web Container
[ http://issues.apache.org/jira/browse/GERONIMO-313?page=comments#action_57855 ] Jeff Genender commented on GERONIMO-313: Chenged the TomcatJAASRealm to take the realm name as a parameter. The LoginContext will look up the security login module by the realm name instead of the app name. This module is complete, but still needs the deployer/builder to set the descriptors to use it. > JAAS Login from Tomcat Web Container > > > Key: GERONIMO-313 > URL: http://issues.apache.org/jira/browse/GERONIMO-313 > Project: Apache Geronimo > Type: Task > Components: web, security, Tomcat > Reporter: David Blevins > Assignee: Alan Cabrera > > At current time any JAAS providers configured with Geronimo are not > leveraged by the Geronimo/Tomcat integration. This work must complete before > Servlet to EJB security propogation can be implemented. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: Apache Naming
On Thu, 20 Jan 2005 11:48:53 -0800, Dain Sundstrom
<[EMAIL PROTECTED]> wrote:
> On Jan 20, 2005, at 11:46 AM, Jeremy Boynes wrote:
>
> > Does anyone know anything about this and whether we should use it in
> > Geronimo?
> >
> > --
> > Jeremy
>
> I don't but I think we should use it :)
I know a bit about it, but remember that we've got direct access to
Alex. FWIW, I have been planning on integrating it into G when I get
the LDAP support into Castor.
Bruce
--
perl -e 'print unpack("u30","<0G)[EMAIL
PROTECTED]&5R\"F9Ehttp://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
[jira] Resolved: (GERONIMO-540) Unable to login to server when using jdk 1.5
[ http://issues.apache.org/jira/browse/GERONIMO-540?page=history ] Jeremy Boynes resolved GERONIMO-540: Resolution: Fixed Fix Version: 1.0-M4 Fix applied in revision 125807 Seems to work on my machine but I'm leaving this open until others can verify. > Unable to login to server when using jdk 1.5 > > > Key: GERONIMO-540 > URL: http://issues.apache.org/jira/browse/GERONIMO-540 > Project: Apache Geronimo > Type: Bug > Components: deployment, security > Versions: 1.0-M4 > Environment: Windows XP / JDK 1.5 > Reporter: Mark DeLaFranier > Assignee: Jeremy Boynes > Fix For: 1.0-M4 > Attachments: my-changes-to-MBeanServerDelegate.patch > > 1. Get the latest codeline (Jan 7/2005) > 2. Do a build > 3. Open a command prompt with JDK 1.5 > > java -version > java version "1.5.0" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64) > Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing) > 4. Start the server > java -jar bin\server.jar org/apache/geronimo/RuntimeDeployer > org/apache/geronimo/DebugConsole > 5. Open a second command prompt and setup the same jdk 1.5 environment > 6. Deploy a sample EJB (dead simple hello world ejb) > > java -jar bin\deployer.jar deploy myejb.jar > Username: system > Password: manager > Error: Unable to connect to server: Invalid login. > I didn't notice any exceptions on the server side and nothing new is sent to > the console or the server log file. > If I used jdk 1.4 to start the server and run the client deployment tool then > it works. > > java -jar bin\deployer.jar deploy myejb.jar > Username: system > Password: manager > Deployed myejb > java version "1.4.2_04" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) > Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-540) Unable to login to server when using jdk 1.5
[ http://issues.apache.org/jira/browse/GERONIMO-540?page=history ] Jeremy Boynes reassigned GERONIMO-540: -- Assign To: Jeremy Boynes > Unable to login to server when using jdk 1.5 > > > Key: GERONIMO-540 > URL: http://issues.apache.org/jira/browse/GERONIMO-540 > Project: Apache Geronimo > Type: Bug > Components: deployment, security > Versions: 1.0-M4 > Environment: Windows XP / JDK 1.5 > Reporter: Mark DeLaFranier > Assignee: Jeremy Boynes > Attachments: my-changes-to-MBeanServerDelegate.patch > > 1. Get the latest codeline (Jan 7/2005) > 2. Do a build > 3. Open a command prompt with JDK 1.5 > > java -version > java version "1.5.0" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64) > Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing) > 4. Start the server > java -jar bin\server.jar org/apache/geronimo/RuntimeDeployer > org/apache/geronimo/DebugConsole > 5. Open a second command prompt and setup the same jdk 1.5 environment > 6. Deploy a sample EJB (dead simple hello world ejb) > > java -jar bin\deployer.jar deploy myejb.jar > Username: system > Password: manager > Error: Unable to connect to server: Invalid login. > I didn't notice any exceptions on the server side and nothing new is sent to > the console or the server log file. > If I used jdk 1.4 to start the server and run the client deployment tool then > it works. > > java -jar bin\deployer.jar deploy myejb.jar > Username: system > Password: manager > Deployed myejb > java version "1.4.2_04" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) > Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: Apache Naming
On Jan 20, 2005, at 11:46 AM, Jeremy Boynes wrote: Does anyone know anything about this and whether we should use it in Geronimo? -- Jeremy I don't but I think we should use it :) -dain
Apache Naming
Does anyone know anything about this and whether we should use it in Geronimo? -- Jeremy
Re: Objectweb annual conference
At 18:00 20/01/2005, Eric Le Goff wrote: > I intend to be there - especially with beer involved :-) Hmm. There was some beer involved, and very intersting food for those who like meat -- uh, I mean MEAT. This was the good side of organizing the conference in Lyon... Too bad I could not find you there, because it was a really nice conference and the ObjectWeb community really diserves congratulations for their organization. Thanks Eric. It was a pleasure to meet you there in person. BTW there was a very interesting BOF about ObjectWeb/Apache collaboration and we were really missing Geronimo committers to illustrate what is a concrete example of collaboration /interactions between the two communities. Previously , Brian Behlendorf was a keynote speaker (about the deeply intertwined relationship between open source software and open standards) but he had to travel to London and could not stay with us. Anyway, I expect to meet geronimo commiters at a future conference such as ApacheCon in Stuttgart (Germany) next summer ;) -- Eric Le Goff http://ericlegoff.homelinux.net François LETELLIER INRIA Rhône-Alpes - ObjectWeb Consortium Executive Committee email: francois.letellier at objectweb.org - phone: +33 (0)6 84 64 00 24 http://www.objectweb.org - ObjectWeb middleware : provide your applications with the kind of freedom they deserve !
Re: Objectweb annual conference
> I intend to be there - especially with beer involved :-) Too bad I could not find you there, because it was a really nice conference and the ObjectWeb community really diserves congratulations for their organization. BTW there was a very interesting BOF about ObjectWeb/Apache collaboration and we were really missing Geronimo committers to illustrate what is a concrete example of collaboration /interactions between the two communities. Previously , Brian Behlendorf was a keynote speaker (about the deeply intertwined relationship between open source software and open standards) but he had to travel to London and could not stay with us. Anyway, I expect to meet geronimo commiters at a future conference such as ApacheCon in Stuttgart (Germany) next summer ;) -- Eric Le Goff http://ericlegoff.homelinux.net
Re: Specs Question.
On Jan 19, 2005, at 10:44 PM, Mark wrote: Quick question regarding specs. My build just failed due to a missing dependency: geronimo-spec-javamail-1.3.1-SNAPSHOT.jar.I went into the geronimo\specs\javamail directory and ran maven which build the missing jar file. I was under the impression that we didn't have to explicitly build the specs anymore. Is this correct? That depends. Sometimes we find bugs in the implementations, and some of the specs are not completely implemented (mostly javamail). It looks like Jeremy has been working on this recently. Personally I always thought the time to rebuild the specs was a small price to pay for avoiding breakage due to spec module updates. thanks david jencks If needed the command line for the main build was: maven -Dmaven.test.skip=true -Dmaven.itest.skip=true clean default Thanks Mark
Re: Specs Question.
Mark wrote:
Quick question regarding specs.
My build just failed due to a missing dependency:
geronimo-spec-javamail-1.3.1-SNAPSHOT.jar.I went into the
geronimo\specs\javamail directory and ran maven which build the missing
jar file. I was under the impression that we didn't have to explicitly
build the specs anymore. Is this correct?
Not sure what happened here - I wiped geronimo and geronimo-spec out of
my local repo and an normal offline build ("maven -o") just built that
module automatically.
I have not pushed the SNAPSHOT to Apache's repo as I am still working on
the implementation.
--
Jeremy
[jira] Commented: (GERONIMO-540) Unable to login to server when using jdk 1.5
[ http://issues.apache.org/jira/browse/GERONIMO-540?page=comments#action_57827 ] Jason Zou commented on GERONIMO-540: When debug using a simple client, the exception trace is as following. It seems JDK 1.5's JMX impl getClassLoaderRepository before auth. I have created a emptyClassLoaderRepository to fix this issue. Now the server can use JDK 1.5's JMX impl instead of Mx4J. Maybe further decision should be made to decide if using JDK 1.5's JMX impl is reasonable. java.lang.SecurityException: Operation not allowed at org.apache.geronimo.kernel.jmx.MBeanServerDelegate.getClassLoaderRepository(MBeanServerDelegate.java:329) at javax.management.remote.rmi.RMIConnectionImpl$2.run(RMIConnectionImpl.java:1281) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.getClassLoaderRepository(RMIConnectionImpl.java:1278) at javax.management.remote.rmi.RMIConnectionImpl.access$000(RMIConnectionImpl.java:81) at javax.management.remote.rmi.RMIConnectionImpl$1.run(RMIConnectionImpl.java:132) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.(RMIConnectionImpl.java:129) at javax.management.remote.rmi.RMIJRMPServerImpl.makeClient(RMIJRMPServerImpl.java:137) at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:230) 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:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:595) > Unable to login to server when using jdk 1.5 > > > Key: GERONIMO-540 > URL: http://issues.apache.org/jira/browse/GERONIMO-540 > Project: Apache Geronimo > Type: Bug > Components: deployment, security > Versions: 1.0-M4 > Environment: Windows XP / JDK 1.5 > Reporter: Mark DeLaFranier > Attachments: my-changes-to-MBeanServerDelegate.patch > > 1. Get the latest codeline (Jan 7/2005) > 2. Do a build > 3. Open a command prompt with JDK 1.5 > > java -version > java version "1.5.0" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64) > Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing) > 4. Start the server > java -jar bin\server.jar org/apache/geronimo/RuntimeDeployer > org/apache/geronimo/DebugConsole > 5. Open a second command prompt and setup the same jdk 1.5 environment > 6. Deploy a sample EJB (dead simple hello world ejb) > > java -jar bin\deployer.jar deploy myejb.jar > Username: system > Password: manager > Error: Unable to connect to server: Invalid login. > I didn't notice any exceptions on the server side and nothing new is sent to > the console or the server log file. > If I used jdk 1.4 to start the server and run the client deployment tool then > it works. > > java -jar bin\deployer.jar deploy myejb.jar > Username: system > Password: manager > Deployed myejb > java version "1.4.2_04" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) > Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-540) Unable to login to server when using jdk 1.5
[ http://issues.apache.org/jira/browse/GERONIMO-540?page=history ] Jason Zou updated GERONIMO-540: --- Attachment: my-changes-to-MBeanServerDelegate.patch J2SE 1.5 getClassLoaderRepository before auth. This patch is to fix it. > Unable to login to server when using jdk 1.5 > > > Key: GERONIMO-540 > URL: http://issues.apache.org/jira/browse/GERONIMO-540 > Project: Apache Geronimo > Type: Bug > Components: deployment, security > Versions: 1.0-M4 > Environment: Windows XP / JDK 1.5 > Reporter: Mark DeLaFranier > Attachments: my-changes-to-MBeanServerDelegate.patch > > 1. Get the latest codeline (Jan 7/2005) > 2. Do a build > 3. Open a command prompt with JDK 1.5 > > java -version > java version "1.5.0" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64) > Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing) > 4. Start the server > java -jar bin\server.jar org/apache/geronimo/RuntimeDeployer > org/apache/geronimo/DebugConsole > 5. Open a second command prompt and setup the same jdk 1.5 environment > 6. Deploy a sample EJB (dead simple hello world ejb) > > java -jar bin\deployer.jar deploy myejb.jar > Username: system > Password: manager > Error: Unable to connect to server: Invalid login. > I didn't notice any exceptions on the server side and nothing new is sent to > the console or the server log file. > If I used jdk 1.4 to start the server and run the client deployment tool then > it works. > > java -jar bin\deployer.jar deploy myejb.jar > Username: system > Password: manager > Deployed myejb > java version "1.4.2_04" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) > Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: Specs Question.
Mark wrote: Quick question regarding specs. My build just failed due to a missing dependency: geronimo-spec-javamail-1.3.1-SNAPSHOT.jar.I went into the geronimo\specs\javamail directory and ran maven which build the missing jar file. I was under the impression that we didn't have to explicitly build the specs anymore. Is this correct? If needed the command line for the main build was: maven -Dmaven.test.skip=true -Dmaven.itest.skip=true clean default There were some changes to JavaMail module and perhaps that's the reason. I don't know how the spec changes are populated to iBiblio.org. I think it's a manual process. Whenever you change the module, you'll have to upload it to iBiblio. Mark Jacek
Specs Question.
Quick question regarding specs. My build just failed due to a missing dependency: geronimo-spec-javamail-1.3.1-SNAPSHOT.jar.I went into the geronimo\specs\javamail directory and ran maven which build the missing jar file. I was under the impression that we didn't have to explicitly build the specs anymore. Is this correct? If needed the command line for the main build was: maven -Dmaven.test.skip=true -Dmaven.itest.skip=true clean default Thanks Mark
[jira] Commented: (GERONIMO-538) Test failures in the security module
[ http://issues.apache.org/jira/browse/GERONIMO-538?page=comments#action_57800 ] Alan Cabrera commented on GERONIMO-538: --- We've changed some of the communication parameters. Can you try again? > Test failures in the security module > > > Key: GERONIMO-538 > URL: http://issues.apache.org/jira/browse/GERONIMO-538 > Project: Apache Geronimo > Type: Bug > Components: buildsystem, security > Versions: 1.0-M4 > Environment: Microsoft Windows 2000 [Version 5.00.2195] SP4 DE > Maven v. 1.0.1 > java version "1.5.0" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64) > Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing) > Reporter: Ralf Barkow > Assignee: Alan Cabrera > Priority: Minor > Attachments: TEST-org.apache.geronimo.security.jaas.TimeoutTest.txt, > geronimo-security-2005-01-02-changes.zip > > The following three unit tests are constantly failing in my environment :- > - org.apache.geronimo.security.jaas.LoginKerberosNonGeronimoTest > - org.apache.geronimo.security.jaas.LoginKerberosTest > - org.apache.geronimo.security.jaas.TimeoutTest > Test-reports :- > - TEST-org.apache.geronimo.security.jaas.LoginKerberosNonGeronimoTest.txt > and > - TEST-org.apache.geronimo.security.jaas.LoginKerberosTest.txt > are empty (0 byte size). > Please find attached the test report of > TEST-org.apache.geronimo.security.jaas.TimeoutTest.txt. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
