Re: Dashboard exception - approvals
Hi,
Indeed there was a configuration issue, which I've now corrected. Here is
a breakdown for future readers:
Retrieving the workflow via: curl -X GET
"http://host:port/syncope/rest/workflows/USER/userWorkflow;
-H "accept: */*" -H "X-Syncope-Domain: Master" -H "Authorization: Basic ..."
revealed the 'userTask' below which has no 'activiti:formKey' attribute.
To resolve the issue, I modified the workflow (restoring the userTask to
the content-less default http://host:port/syncope/rest/workflows/USER/userWorkflow; -H
"accept: */*" -H "X-Syncope-Domain: Master" -H "Authorization: Basic ..."
-H "Content-Type: application/xml" -d "http://host:port/syncope/rest/userworkflow/forms;
-H "accept: application/json" -H "X-Syncope-Domain: Master" -H
"Authorization: Basic ..."
which contained the null key, but also the affected new user key.
[
{
"username": ".",
"taskId": "7554",
"key": null,
"createTime": "2018-04-17T14:23:06.080+",
"dueDate": null,
"owner": null,
"userTO": {
"@class": "org.apache.syncope.common.lib.to.UserTO",
"key": "db1ab1a4-0e2f-422e-9ab1-a40e2fb22e4a",
"type": "USER",
I then deleted the user with:curl -X DELETE "http://host:port/syncope/
rest/users/db1ab1a4-0e2f-422e-9ab1-a40e2fb22e4a" -H "accept:
application/json" -H "Prefer: return-content" -H "X-Syncope-Domain: Master"
-H "Authorization: Basic ..."
and was able to login to the console to try again.
Thanks as always for all your guidance.
Dave
Re: ApacheCon current-event banner
Ciao Piergiorgio, I have just updated our website to comply with ASF policies, including Events. Regards. On 17/04/2018 22:02, Piergiorgio Lucidi wrote: Hi, I'm contributing in the Apache ComDev project and we would like to spread out informations about Apache-related events such as ApacheCon. Rich Bowen started a thread about this topic and we are actually searching to use a dynamic banner that will be updated automatically without the need to update the website everytime for every new event. On the dev@community.a.o list Rich Bowen asked to get this included in as many project websites as possible [2]. It would be great to have also Syncope website updated to include the current-event banner described in the first step of this README [1]. To track the progress of all projects updating their website, a link to this thread will be put in a shared google spreadsheet [3]. Thank you so much for your cooperation. Cheers, PJ [1] - http://apache.org/events/README.txt [2] - https://lists.apache.org/thread.html/d672b1849f6668c0f67ff4c71b20bbb4f56a49a1777607b12643d1dc@%3Cdev.community.apache.org%3E [3] - https://docs.google.com/spreadsheets/d/101O3EVBYv_QhHW74bFLoO89ydaXoUJW4AC97YhnR530/edit#gid=0 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Dashboard exception - approvals
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
https://github.com/apache/syncope/blob/2_0_X/core/workflow-activiti/src/main/java/org/apache/syncope/core/workflow/activiti/ActivitiUserWorkflowAdapter.java#L550
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 http://syncope-vm.apache.org:9080/syncope/rest/openapi.json for
example, I can see that the value is
"servers": [
{
"url": "http://syncope-vm.apache.org:9080/syncope/rest;
}
],
Such value is dynamically derived from the URL used to access the
openapi.json resource, and is set by CXF in
https://github.com/apache/cxf/blob/3.1.x-fixes/rt/rs/description-swagger/src/main/java/org/apache/cxf/jaxrs/swagger/openapi/SwaggerToOpenApiConversionUtils.java#L418-L446
Possibly, the method use to reconstruct the request URL does not work
properly with your reverse proxy setup.
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
[jira] [Commented] (SYNCOPE-1299) Manual reconciliation
[ https://issues.apache.org/jira/browse/SYNCOPE-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442143#comment-16442143 ] ASF subversion and git services commented on SYNCOPE-1299: -- Commit 8e7bf8a499609c9b9c12119e90258c41f65f46eb in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=8e7bf8a ] [SYNCOPE-1299] Small cleanup > Manual reconciliation > - > > Key: SYNCOPE-1299 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1299 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.9, 2.1.0 > > > Provide the feature - in Admin Console from either an User / Group / Any > Object and from an External Resource (under Topology) - which, given a User / > Group / Any Object and an External Resource, allows to force pushing or > pulling values for mapped attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1299) Manual reconciliation
[ https://issues.apache.org/jira/browse/SYNCOPE-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442142#comment-16442142 ] ASF subversion and git services commented on SYNCOPE-1299: -- Commit c60210d3c747acd448dc805834a85d2833b146fe in syncope's branch refs/heads/2_0_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=c60210d ] [SYNCOPE-1299] Small cleanup > Manual reconciliation > - > > Key: SYNCOPE-1299 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1299 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.9, 2.1.0 > > > Provide the feature - in Admin Console from either an User / Group / Any > Object and from an External Resource (under Topology) - which, given a User / > Group / Any Object and an External Resource, allows to force pushing or > pulling values for mapped attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
