OpenSSO Extensions

OpenSSO Extensions FAQ

  1. What are OpenSSO Extensions?
  2. Where are OpenSSO Extensions stored?
  3. How does OpenSSO Extensions compare to Lightbulb?
  4. Can I contribute to OpenSSO Extensions?
  5. Can the code in OpenSSO Extensions become part of the OpenSSO product?

Q: What are OpenSSO Extensions?

OpenSSO Extensions is an incubator for modules that build on the access control, single sign-on and federation technology in OpenSSO, but are not part of the core project. As OpenSSO Extensions is not part of the core OpenSSO product tree, the rules are more relaxed for code review and check in.

Q: Where are OpenSSO Extensions stored?

OpenSSO Extensions are checked into the extensions subtree.

Q: What is Lightbulb and how does it compare to OpenSSO Extensions?

Lightbulb was intended to be a set of sub-projects that focused on implementing federation technologies for the Linux, Apache, MySQL, PHP (LAMP) stack; the name was intended as a pun. The initial sub-project was a SAML version 2.0 service provider developed using PHP. As the number of potential contributions has grown to encompass modules that build on OpenSSO without targeting LAMP, we decided to change the name.

Q: Can I contribute to OpenSSO Extensions?

Yes. Contributions are welcome! The Sun Contributor Agreement applies to OpenSSO Extensions, just as it does to the OpenSSO core, but the relaxed governance is intended to encourage widespread participation.

Q: Can the code in OpenSSO Extensions become part of the OpenSSO product?

Another yes. The mechanism for promotion (besides a consensual decision by the OpenSSO team) would be to simply move a subtree from opensso/extensions to opensso/product.