I am looking to permit the OPTIONS calls to the Flowable REST server so as to make cross domain requests (my Flowable server is hosted on a different domain) to this server.
I figured this change in the source code could help, but it is not doing the job. Is there something amiss in my configuration?
From a first glance, that seems to be ok. Are you sure the changes are picked up?
Did you put spring security on debug log level … if so, what happens for such a request?
Hi @joram,
How do I go about doing this in Flowable? I inserted log4j.logger.org.springframework.security=DEBUG in /webapps/flowable-rest/WEB-INF/classes/log4j.properties file, restarted the Tomcat service. I don’t see any debug information related to Spring security.
i was looking at your diff.
Can you explain what you’re trying to do? And in what app(s)?
The class your modifying is part of the flowable-rest-app. But you’re referring ‘/flowable-task’. This mapping is not present in the Flowable REST APP. This is part of the Flowable Task UI APP.
Take a look here to see how the REST APIs are mapped in the REST APP.
The mapping you’re using seems to be one used in the TASK UI APP. The same APIs are exposed in here; but with a different mapping.
Hello @yvo,
In a sentence: I want to be able to allow cross origin requests to my Flowable server hosted on a different domain. This means that HTTP OPTIONS verb should be allowed without any Basic Authentication.
I am using /flowable-task based on the flowable-ui-app.properties file present in the flowable-admin app - which says Default REST endpoint config. This obviously seems to be the source of the problem.
I changed the URI to /service/process-api/query/process-instances and the the code change that I made works now.