Ovidiu, you are welcome to use this forum to discuss the features and patches. We will certainly include good features and bug fixes in future releases.
Features that come up when working on the field are usually good stuff to include as they reflect the needs from the end users. I think your idea of splitting the discussion in several sub threads is really good because it will make the discussions more focused.
Please find below:
As mentioned on each individual issue, I have patches that have been tested and are ready to be applied, as soon as the Security team agrees that all (or some) of the above are good ideas. Please let me know, I am standing by.
I've posted a reply to each one of the threads. With the exception of the second thread (client auth option in JaasSecurityDomain) I think all the features are pretty useful and we should include them.
Great, thank you.
I'll create JIRA issues for 1. 3. and 4. You mentioned that I can commit directly. Where? (alternatively, I can attach patches, but committing directly it's a lot better).
As for 2, I'll continue the discussion on the thread.
Ovidiu, most of the code you'll be touching (org.jboss.security.ssl.*, JaasSecurityDomain) is located in the application server security module (trunk/security). However, the SecurityDomain interface is defined in the security-spi project, so the first thing we have to do is to apply all the needed changes to this interface and then cut a release of the security project. After that we can update the AS and perform the remaining changes.
Let me know when you're done so I can cut the release for you.