API Orchestrator Post Request with FormCycle

Hi,

we use the FormCycle software. There is the possibility to start a post request and I am currently trying to set it up. Here I try to work with an “HTTP Basic Authentication”, but I get the following error:

java.io.IOException: Server returned error-status: 401
   at de.xima.fc.http.PostRequestBuilder.build(PostRequestBuilder.java:269)
   at de.xima.fc.bl.fdv.processing.VerarbeitungPost.exec(VerarbeitungPost.java:251)
   at de.xima.fc.bl.fdv.processing.AVerarbeitung.execute(AVerarbeitung.java:43)
   at de.xima.fc.bl.fdv.WorkflowProcessing.exec(WorkflowProcessing.java:433)
   at de.xima.fc.bl.fdv.WorkflowProcessing.processVorgang(WorkflowProcessing.java:271)
   at de.xima.fc.bl.fdv.WorkflowProcessing.process(WorkflowProcessing.java:640)
   at de.xima.fc.bl.WorkflowStarter.initWorkflowProcessing(WorkflowStarter.java:175)
   at de.xima.fc.bl.WorkflowStarter.initWorkflow(WorkflowStarter.java:71)
   at de.xima.fc.form.FormProcessDataBuilder.build(FormProcessDataBuilder.java:62)
   at de.xima.fc.handler.system.FormHandler.loadFormProcessData(FormHandler.java:44)
   at de.xima.fc.api.system.FormAPI.loadFormProcessData(FormAPI.java:31)
   at de.xima.fc.form.process.FormProcessContextBuilder.build(FormProcessContextBuilder.java:94)
   at de.xima.fc.form.process.FormProcessContextBuilder.build(FormProcessContextBuilder.java:64)
   at de.xima.fc.servlet.AFormProcessingServlet.processSubmit(AFormProcessingServlet.java:327)
   at de.xima.fc.servlet.AFormProcessingServlet.startVorgang(AFormProcessingServlet.java:247)
   at de.xima.fc.servlet.AFormProcessingServlet.processHttp(AFormProcessingServlet.java:178)
   at de.xima.fc.servlet.AFormProcessingServlet.exec(AFormProcessingServlet.java:146)
   at de.xima.fc.servlet.AFormProcessingServlet.process(AFormProcessingServlet.java:122)
   at de.xima.fc.servlet.AFormProcessingServlet.doPost(AFormProcessingServlet.java:83)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
   at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
   at de.xima.fc.servlet.filter.AutoLoginFilter.doFilter(AutoLoginFilter.java:61)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
   at de.xima.fc.servlet.filter.GlobalSecurityFilter.doFilter(GlobalSecurityFilter.java:64)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
   at de.xima.fc.servlet.filter.GlobalServerInfoFilter.doFilter(GlobalServerInfoFilter.java:65)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
   at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:176)
   at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145)
   at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92)
   at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:389)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
   at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
   at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
   at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
   at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
   at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
   at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688)
   at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
   at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:747)
   at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
   at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:375)
   at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
   at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:869)
   at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639)
   at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
   at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
   at java.base/java.lang.Thread.run(Thread.java:829)

When I check, the 401 means the login doesn’t work. Here are the settings for the post request:

The server URL and login is correct and working. I have used this same post request somewhere else but only with a different parameter but with a bearer token as authentication before. Would a normal “HTTP Basic Authentication” work at all in connection with an OnPremise Orchestrator?

Hi!

Could you see if you can authenticate the user?
Just check your on-premise swagger for details, just paste this in your browser {on-premiseURL}/swagger
And is your URL correct?

As I said, the user and server address is correct. I already use both data in another process, just without the “FormCycle” software.

Hi!

Just checking.

Have you used the “FormCycle” software to try and run this API-call?
As stated in my previous post see your on-premise swagger for details.

If I remember correctly this will return a 0auth token which you can use in subsequent calls.