Bug 823318
Summary: | jBPM console cannot initialize session when drools packages are signed | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Jiri Locker <jlocker> | ||||
Component: | jBPM Console | Assignee: | Maciej Swiderski <mswiders> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Lukáš Petrovický <lpetrovi> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | BRMS 5.3.0.GA | CC: | atangrin, mswiders | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-05-22 17:41:29 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Jiri Locker
2012-05-20 21:50:40 UTC
I beleive this is not related to loading packages from guvnor but loading session from data base. What is happening is that session was persisted without signature before and after security was enhanced (sign serialization was enabled)session cannot be loaded as it was stored not signed, thus we see this error message. Could you please confirm/refute above? I will work on setting up the environment as described. After setting up environment with security enabled I confirm that it will fail if console will try to load session that was created (and persisted) with security disabled. Due to that there is a need to enforce console to create new session instead of loading one after turning security on. This can be done by deleteing jbpmSessionId.ser file that is located in {jboss.server.temp.dir} After this has been done, console is capable to read signed packages from guvnor and load the signed session. I didn't mention the method I used to set serialization properties. I only placed them into jboss-brms.war/WEB-INF/classes/preferences.properties. Therefore I expected that only Guvnor would know signing is enabled. I didn't know that org.drools.guvnor.server.configurations.ApplicationPreferencesInitializer is used to set these preferences as System properties and so the environment was really configured to work with signed objects when the session was loaded by jbpm console. Now I understand this issue is not a bug and only occurs when the console loads the session and signing preference was changed before the session was created. |