7 Replies Latest reply on Sep 25, 2006 1:04 AM by anil.saldhana

    Split of Security Project into SPI and JBossAS Implementatio

    anil.saldhana

      This affects JBossAS HEAD only.

      Scott has expressed a need to split the security project artifacts into spi and JBossAS implementation (or plugins). These need to be downloadable via the JBoss repository into JBossAS as well as other JEMS projects.

      Given this, I would like to point to the following JIRA issue:
      http://jira.jboss.com/jira/browse/SECURITY-1

      The end result will be that the security module will be moved out of jbossas/trunk and will be available under projects. The security spi jars as well as the JBossSX jars will be downloaded via the thirdparty mechanism.

      The idea is that JEMS projects(or system integrators) should be able to code to the Security SPI.

      The whole thing will be done by COB September 8,2006 (Friday)

        • 1. Re: Split of Security Project into SPI and JBossAS Implement
          anil.saldhana

           

          The Security module has been moved out of JBossAS *trunk* into jbossas/projects (similar to the microcontainer).
          
          What does this mean?
          - There are two projects? artifacts downloaded from the third party repository. One is the Security SPI (security-spi) and the other is the JBossAS implementation (security)
          - Dependent projects in jbossas will make use of the artifacts from security. If there are any projects that have an implementation of the SPI (like the ejb3 project), then they will make additional use of security-spi artifacts.
          
          What is the motivation?
          Having a SPI allows JEMS projects as well as service integrators to provide an alternative implementation (and not necessarily use the JBossAS implementation aka jbosssx.jar)
          
          Did it screw up eclipse settings?
          I have updated the .classpath file for projects in jbossas that make use of security. Please verify.
          
          Does it affect the branches (3.2 and 4.0)
          No
          
          Is the SPI fixed?
          Not yet. It is evolving(http://www.jboss.com/index.html?module=bb&op=viewtopic&t=81097)
          
          Troubleshooting:
          a) If workspace does not build, nuke third party folder and do a clean build.
          b) Tests are failing ? inform. (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90069)
          
          



          Additional note:
          What are the artifacts?
          asaldhana~/jboss-5.0/jboss-head/thirdparty>cd jboss/security-spi/
          asaldhana~/jboss-5.0/jboss-head/thirdparty/jboss/security-spi>ls lib
          jboss-security-spi.jar
          
          asaldhana~/jboss-5.0/jboss-head/thirdparty/jboss/security>
          asaldhana~/jboss-5.0/jboss-head/thirdparty/jboss/security>ls lib
          jbosssx-client.jar jbosssx.jar
          


          QA Validation JIRA issue:
          http://jira.jboss.com/jira/browse/JBQA-461

          • 2. Re: Split of Security Project into SPI and JBossAS Implement
            starksm64

            I updated the project to have a valid eclipse project setup. We need to convert this to maven2 and remove these jars as they need to come from the repository. What is the reason for including the jars with ? by them?

            jboss-auth.jar
            jboss-j2ee.jar
            jboss-j2se.jar ?
            jboss-jaxrpc.jar ?
            jboss-jmx-compliance.jar ?
            jboss-mbeans.jar
            jboss-saaj.jar ?
            jboss-system.jar
            jboss-transaction.jar ?
            jnpserver.jar
            



            • 3. Re: Split of Security Project into SPI and JBossAS Implement
              anil.saldhana

              Must be a copy oversight (as surely security does not depend on Saaj)

              • 4. Re: Split of Security Project into SPI and JBossAS Implement
                devobject

                Hi Guys,

                Are you working on SSO Module of JEMS Platform. I just like inform to review Siteminder SSO Framework API. I just implemented this api with Commerce One Platform in 2004. It real nice architecture to provided security various level for variouse domain suck bank,telecom, enterprise.

                -Praful
                6474005250
                Canada.

                • 5. Re: Split of Security Project into SPI and JBossAS Implement
                  soshah

                  Praful-

                  We have a Federated Single Sign On Project in active development.

                  Here are the JIRA details of this project:

                  http://jira.jboss.com/jira/browse/JBSSO

                  The SiteMinder API that you have developed/addressed in this thread could be a very useful addition to the Identity Management Framework component of the project.

                  We currently have support for LDAP directories, and we are always looking to expand integration with other Identity Stores.

                  Thanks
                  Sohil

                  • 6. Re: Split of Security Project into SPI and JBossAS Implement
                    anil.saldhana

                    Why is this design thread hijacked? Use the JBoss Security User Forum, Praful.

                    • 7. Re: Split of Security Project into SPI and JBossAS Implement
                      anil.saldhana

                      http://jira.jboss.com/jira/browse/SECURITY-9

                      The first cut of the maven pom.xml has been checked in.

                      Question is: do we need a rmic plugin(there is none existing for M2) to compile the SRPRemoteServer stubs? Scott, it is not clear to me whether the varia module alone deals with SRP* or the security module also has SRP.