-
1. Re: jbpm-console login process issued a wrong resteasy call
heiko.braun Oct 21, 2009 6:52 AM (in response to washawu)What steps did you follow to setup jbpm on websphere? Can you execute the examples? AFAIK jbpm installation on websphere has not been tested.
-
2. Re: jbpm-console login process issued a wrong resteasy call
washawu Oct 21, 2009 12:07 PM (in response to washawu)Thanks for your quick reply. I was able to deploy jbpm4.1 on WebSphere7.0 after struggling with WebSphere custom registry setup to adapt the jbpm access control. Without making any changes to the jbpm-console.war, gwt-console-server.war and following the instruction, now I am able to run most of the functions on the jbpm-console.
The only problem I found is that I cannot re-login to the console without clearing bowser history on Firefox, on IE, I have to restart the browser every time to login. When I try to login the 2nd time on FF, I am getting this response: http://localhost:9081/gwt-console-server/rs/identity/sucure/ 405 Method Not Allowed, in FireBug. It seams like the gwt-console-server login information or cookies information is not being cleared after every login. Please help to identify this problem. Also please tell me how to deploy and configure the jbpm-consol onto a separate server, if possible. Do you have a document on the security setup?
I have a thought about the jbpm build-in security mechanism. Most of the features in jbpm are very easy to deploy and use, except the console security. Security feature should be packaged as a separate add-on, plug-in, i.e. using Spring security. If an open source project is developed as application server independent, it will quickly increase its popularity and adaptability.
Thank you and best regards. -
3. Re: jbpm-console login process issued a wrong resteasy call
heiko.braun Oct 29, 2009 4:59 AM (in response to washawu)There is nothing special about the GWT console security. It simply uses JAAS. Take a look at the web.xml, IMO it's self explaining.