Hi
-- We are currently using Orbeon Forms version 4.1.0.201304182144-PE and we are attempting to use the schema generation service introduced in 4.0PE. Whenever we call the service we pass in preemptive basic credentials. These credentials are for the role orbeon-service. We have successfully used the same credentials in order to perform crud operations against the REST API however we cannot get the correct response back for the schema generation service. Whenever we call the service GET http://<service-end-point>/orbeon/fr/<app-name>/<form-name>/schema HTTP/1.1 we receive a 403 error: HTTP/1.1 403 Forbidden Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=D7B1F340329B92FBD22F74E388B12B36; Path=/orbeon/; HttpOnly Content-Length: 0 Date: Fri, 25 Oct 2013 10:02:59 GMT Whereas whenever we call the service GET http://<service-end-point>/orbeon/fr/service/schema/<app-name>/<form-name> HTTP/1.1 we receive a 404 error: HTTP/1.1 404 Not Found Note #1 - We have used two different GET requests as the following pages describing the usage document different URIs for the service: http://wiki.orbeon.com/forms/doc/developer-guide/form-runner/xml-schema-service http://blog.orbeon.com/2013/05/automatic-schema-generation-for-forms.html Note #2 - The form that we are attempting to generate a schema for was built using Orbeon Form builder and has 2 text boxes and 2 date components. Note #3 - We have removed all of the demo applications/forms for this Orbeon installation in accordance with the user guide. We are presuming that the schema generation service is part of the core of Orbeon. Many thanks Graham You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
Administrator
|
Graham,
Are you using orbeon-auth.war? If so, the security constraint has: <web-resource-collection> <web-resource-name>Form Runner services</web-resource-name> <url-pattern>/fr/service/*</url-pattern> </web-resource-collection> That could explain why the authorization fails as the schema service is not available under that path (which also explains the 404 error in the other case). But it should be and I entered a bug: https://github.com/orbeon/orbeon-forms/issues/1367 Regards, -Erik |
Hi Eric
-- Thanks for your response. Yes, we are using orbeon-auth.war and we have added a tomcat user (name = orbeon-authenticator, roles = orbeon-service, along with a password). We have successfully used these credentials to perform CRUD operations against the REST API. We've created new instances of form submissions as well retrieved existing form definitions. I've attached copies of the web.xml files that we are using. As far as we can tell they are unchanged from the files provided in Orbeon Forms 4.1.0.201304182144-PE. Do we simply need to modify the main Orbeon web.xml in order to publish the schema service, as well as adding the role "orbeon-user" to our orbeon-authenticator tomcat user in order to resolve this issue in 4.1.0.201304182144-PE? Many thanks Graham On Monday, 28 October 2013 17:49:00 UTC, ebruchez wrote: Graham, You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
Administrator
|
Graham,
I don't know if there is a simple fix for Orbeon Forms 4.1. What needs to be done is to manage to authorize the schema service. But because of the limitations (euphemism) of the web.xml format, I am not sure it's possible via simple changes to web.xml. You could authorize individual forms, e.g. matching /fr/app/form1/schema, etc. in the orbeon-auth.war web.xml. That should work as you can match on the whole path. The fix implemented for 4.4 is better I think, because it allows matching globally on /fr/service/* to authorize all services. -Erik |
Free forum by Nabble | Edit this page |