[JBoss JIRA] Created: (JBRULES-3155) Bug with default properties in KnowledgeStoreServiceImpl
by Pavel Sknar (JIRA)
Bug with default properties in KnowledgeStoreServiceImpl
--------------------------------------------------------
Key: JBRULES-3155
URL: https://issues.jboss.org/browse/JBRULES-3155
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.2.0.Final
Reporter: Pavel Sknar
Assignee: Mark Proctor
Priority: Critical
Method setDefaultImplementations() set default properties in configProps (class KnowledgeStoreServiceImpl). mergeConfig() execute after specific properties loaded to configuration. This overlaps specific properties.
[17:08] <pavlz> hi
[17:09] <pavlz> I have bug for you
[17:09] <Rikkola> :(
[17:10] <pavlz> Problem with KnowledgeStoreServiceImpl
[17:10] <pavlz> in org.drools.persistence.jpa
[17:12] <pavlz> default properties merged first in config (in ChainedProperties: this.props.add( 0, properties ))
[17:14] <pavlz> and this overlaps specific properties
[17:15] <pavlz> drools.commandService, drools.timerService and else
[17:15] <pavlz> I have this bug in 5.2.0.Final
[17:23] <conan> pavlz: do you have a fix?
[17:25] <pavlz> No, I see this now
[17:27] <pavlz> but I think: need to create in ChainedProperties new method "setDefaultProperties"
[17:29] <pavlz> and in SessionConfiguration too, to use this method in KnowledgeStoreServiceImpl.mergeConfig()
[17:30] <pavlz> then default properties loaded later
[17:31] <Rikkola> pavlz: best to make a jira about it
[17:31] <Rikkola> https://issues.jboss.org/browse/JBRULES
[17:31] <pavlz> ok
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (AS7-3691) A Negotiated HTTP Authenticator
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-3691:
-------------------------------------
Summary: A Negotiated HTTP Authenticator
Key: AS7-3691
URL: https://issues.jboss.org/browse/AS7-3691
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Security, Web
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Historically we have become constrained by an assumption that there should be a single authentication mechanism assigned to a web application.
The HTTP specification however allows for multiple mechanisms to be used in parallel - this task is to investigate the feasibility of writing a single authenticator that is compatible with both JBoss Web and the Sun HTTP server used within AS7 to support a negotiated authentication using a single authenticator backed by a CallbackHandler based realm.
The most common example is fallback from SPNEGO to a username / password based mechanism but for domain management we have also a case of trying to use CLIENT-CERT authentication first and then fallback if that is not possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months