8 Replies Latest reply on Apr 16, 2008 3:49 PM by Sohil Shah

    Federation 1.0 CR1 & jboss 4.2.1

    Nat Newbie

      Hi!
      I try to use jboss 4.2.1 + Federation 1.0 CR1+ win xp
      and I have problem as:
      http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029733#4029733

      Help me please! Patch?

        • 1. Re: Federation 1.0 CR1 & jboss 4.2.1
          Alejandro Montenegro Novice

          did you read the Readme.txt file that comes with the bundle?

          can you post the error, so we can evaluate what happens.

          • 2. Re: Federation 1.0 CR1 & jboss 4.2.1
            Nat Newbie

             

            "aamonten" wrote:
            did you read the Readme.txt file that comes with the bundle?

            Yes. But patches are for Jboss 4.0.4 and 4.0.5. Not for Jboss 4.2.1!

            can you post the error, so we can evaluate what happens.


            I've amended the windows hosts file as suggested in order to simulate two domains.
            I've started each instance with "run -c default -b node1.jboss.com" and "run -c default2 -b node1.jboss.org" respectively.

            I am then able to access the application, and login successfully with the credentials user1:password, on the first instance using the URL:
            http://node1.jboss.com:8080/test

            However, when I then attempt to click on the "Cross Domain Get Tester" link, I get the following exception on the second instance (default2):

            2007-03-20 11:00:14,711 ERROR [org.opensaml.SAMLObject] caught an exception while parsing a stream:
            XML document structures must start and end within the same entity.
            2007-03-20 11:00:14,727 ERROR [org.jboss.security.federation.servlet.SSOFederationServer] org.jboss.
            security.federation.servlet.SSOFederationServer@126f304
            org.jboss.security.saml.SSOException: org.xml.sax.SAXParseException: XML document structures must st
            art and end within the same entity.
            at org.jboss.security.saml.JBossSingleSignOn.parseAuthResponse(JBossSingleSignOn.java:343)
            at org.jboss.security.sso.util.SSOUtil.getUsername(SSOUtil.java:119)
            at org.jboss.security.federation.servlet.SSOFederationServer.doPost(SSOFederationServer.java:158)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252
            )
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
            at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202
            )
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
            at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
            at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
            at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)

            at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
            at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
            at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
            at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
            at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
            at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11Base
            Protocol.java:664)
            at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
            at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
            at java.lang.Thread.run(Thread.java:595)
            Caused by: org.xml.sax.SAXParseException: XML document structures must start and end within the same
            entity.
            at org.opensaml.SAMLObject.fromStream(Unknown Source)
            at org.opensaml.SAMLResponse.(Unknown Source)
            at org.jboss.security.saml.JBossSingleSignOn.parseAuthResponse(JBossSingleSignOn.java:281)
            ... 23 more

            =======================================
            Need patch for Jboss 4.2.1?

            • 3. Re: Federation 1.0 CR1 & jboss 4.2.1
              Mauricio Salatino Master

              i'm running with JBoss 4.2.2.GA and works fine...
              did you try to log in both http://node1.jboss.com:8080/test and
              http://node1.jboss.org:8080/test separately?

              • 4. Re: Federation 1.0 CR1 & jboss 4.2.1
                Nat Newbie

                 

                "salaboy21" wrote:
                i'm running with JBoss 4.2.2.GA and works fine...
                did you try to log in both http://node1.jboss.com:8080/test and
                http://node1.jboss.org:8080/test separately?



                Yes. Log in separately OK.

                • 5. Re: Federation 1.0 CR1 & jboss 4.2.1
                  Nat Newbie

                   

                  "salaboy21" wrote:
                  i'm running with JBoss 4.2.2.GA and works fine...
                  did you try to log in both http://node1.jboss.com:8080/test and
                  http://node1.jboss.org:8080/test separately?



                  I try start wiht JBoss 4.2.2 and works OK!
                  Thank You!!! :-)

                  • 6. Re: Federation 1.0 CR1 & jboss 4.2.1
                    Mauricio Salatino Master

                    Great news! i think JBoss AS 4.2.2.GA has patched.. but i'm not really sure if thats the problem...
                    Let me know if you have some trouble with SSO

                    • 7. Re: Federation 1.0 CR1 & jboss 4.2.1
                      Alejandro Montenegro Novice

                      Ok, I will comment that on the jira, this should not be a priority to fix then.

                      • 8. Re: Federation 1.0 CR1 & jboss 4.2.1
                        Sohil Shah Master

                        Guys-

                        This issue is fixed on the JBoss SSO trunk located at:

                        http://anonsvn.jboss.org/repos/jboss-sso/dev/trunk

                        Its commit # 118 labeled [Establishing Baseline JBoss AS Support - Supports JBoss AS 4.x series - (4.0.4.GA and higher)]

                        It will be included in the next release

                        Thanks