syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò <>
Subject Re: Dashboard exception - approvals
Date Wed, 18 Apr 2018 10:52:47 GMT
On 18/04/2018 01:14, Dave Varon wrote:
> Hi,
> The response body (pretty print at bottom) does in fact contain
> "key":null.   FWIW there are no derived or virtual schemas, or groups
> configured, 'email' is the only plain schema, and there are no resources.

That 'key' value is only set by

with the value coming from the actual form definition.

I suspect that there is something wrong in your current workflow 
definition: could you please provide it?

> FYI some tangential weirdness:  tomcat/syncope is sitting behind apache
> httpd. If I use the default port (443), either explicitly or implicitly,
> the server url constructed for swagger is "https://host:-1/syncope/rest".
> This seems broken.  Çan it be resolved somehow?  I couldn't find any
> config.  As one might expect, this results in 404.
> This is obv not a problem with curl, nor if I connect to tomcat directly in
> browser on non-ssl port 8000

Swagger UI relies on /syncope/rest/openapi.json, the servers > url 
field, to construct the URLs.
 From for 
example, I can see that the value is

"servers": [
"url": ""

Such value is dynamically derived from the URL used to access the 
openapi.json resource, and is set by CXF in

Possibly, the method use to reconstruct the request URL does not work 
properly with your reverse proxy setup.


Francesco Chicchiriccò

Tirasa - Open Source Excellence

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail

View raw message