[ https://jira.jboss.org/jira/browse/JBESB-3190?page=com.atlassian.jira.plu... ] Jeff DeLong commented on JBESB-3190: ------------------------------------ I should add some justification for this request: 1) It is provided my jUDDI 2) customers expect JBoss to provide integration with JBoss JAAS 3) Apache jUDDI web site specifically states jUDDIAuthentication is not for production use 4) If customers want to use jUDDI for registration of their web services, they will expect to have some control over which users can publish these services to the registry. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-3190?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-3190: ------------------------------------- It should be a simple matter of changing the juddi config to enable this as we do not circumvent the normal juddi mechanism. It is probably better to chase any 'production' issues up through the SOA platform, rather than the project, as they will be the ones responsible for handling consistency across projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-3190?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-3190: ------------------------------------- Relates to SOA-1865 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira