[jboss-dev-forums] [Design of Security on JBoss] - Re: JBoss Negotiation - 2.0.3.Beta2 released, onto 2.0.3.CR1

"darran.lofthouse(a)jboss.com" wrote : The Beta2 release is now out https://jira.jboss.org/jira/browse/SECURITY-266, so now onto the tasks for the CR1 release (Which should be a real CR release with the potential to be tagged GA). | | I think the following tasks are the important ones. | | - Documentation | + Formatting for PDF | + Additional References | | - Jira Issues | + Review all issues for relevance | | This one needs to be reviewed https://jira.jboss.org/jira/browse/SECURITY-138 | | This may be required https://jira.jboss.org/jira/browse/SECURITY-141 but I think the fallback solution should possibly be a bit more generic - overall I don't think this is a blocker for the first CR/GA release. | | - Packaging / Release | + How is this going to be packaged? | + Where will the release be uploaded to? | + The build needs to be able to create the distribution. | | Any further comments / requirements for the CR / GA release? | | | I don't know if this is the place to ask for this, so I apology if this is not the place. Would it be possible to authenticate against more than one KDC server? For example, suppouse we have three center, each one with its own AD. The users from each center log in different domains (The one that corresponds with their AD), but there is a server (The one we want to use SPNEGO) that should be able to authenticate the user against the corresponding AD. Can this be done? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174149#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...