Re: Dashboard exception - approvals
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.
[{"username":"varontron","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","realm":"/SRP","username":"varontron","creator":null,"creationDate":"2018-04-17T14:23:06.138+","lastModifier":null,"lastChangeDate":"2018-04-17T14:23:06.138+","status":null,"password":"xxx","token":null,"tokenExpireTime":null,"lastLoginDate":null,"changePwdDate":null,"failedLogins":null,"securityQuestion":"48400a54-6910-4237-800a-5469109237ee","securityAnswer":"","suspended":false,"mustChangePassword":false,"dynRealms":[],"auxClasses":[],"plainAttrs":[{"schemaInfo":null,"schema":"email","values":["
varont...@gmail.com"]}],"derAttrs":[],"virAttrs":[],"resources":[],"roles":[],"dynRoles":[],"relationships":[],"memberships":[],"dynMemberships":[]},"userPatch":null,"workflowFormProperties":[{"id":"username","name":"Username","type":"String","value":"varontron","readable":true,"writable":false,"required":false,"datePattern":null,"enumValues":{}},{"id":"approve","name":"Approve?","type":"Boolean","value":null,"readable":true,"writable":true,"required":true,"datePattern":null,"enumValues":{}},{"id":"rejectReason","name":"Reason
for
rejecting","type":"String","value":null,"readable":true,"writable":true,"required":false,"datePattern":null,"enumValues":{}}]}]
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
Thanks,
Dave
[
{
"username": "varontron",
"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",
"realm": "/SRP",
"username": "varontron",
"creator": null,
"creationDate": "2018-04-17T14:23:06.138+",
"lastModifier": null,
"lastChangeDate": "2018-04-17T14:23:06.138+",
"status": null,
"password": "xxx",
"token": null,
"tokenExpireTime": null,
"lastLoginDate": null,
"changePwdDate": null,
"failedLogins": null,
"securityQuestion": "48400a54-6910-4237-800a-5469109237ee",
"securityAnswer": "",
"suspended": false,
"mustChangePassword": false,
"dynRealms": [],
"auxClasses": [],
"plainAttrs": [
{
"schemaInfo": null,
"schema": "email",
"values": [
"varont...@gmail.com"
]
}
],
"derAttrs": [],
"virAttrs": [],
"resources": [],
"roles": [],
"dynRoles": [],
"relationships": [],
"memberships": [],
"dynMemberships": []
},
"userPatch": null,
"workflowFormProperties": [
{
"id": "username",
"name": "Username",
"type": "String",
"value": "varontron",
"readable": true,
"writable": false,
"required": false,
"datePattern": null,
"enumValues": {}
},
{
"id": "approve",
"name": "Approve?",
"type": "Boolean",
"value": null,
"readable": true,
"writable": true,
"required": true,
"datePattern": null,
"enumValues": {}
},
{
"id": "rejectReason",
"name": "Reason for rejecting",
"type": "String",
"value": null,
"readable": true,
"writable": true,
"required": false,
"datePattern": null,
"enumValues": {}
}
]
}
]
An
ApacheCon current-event banner
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
Re: Misleading policy documentation (minor)
On 17/04/2018 17:45, Dave Varon wrote:
Yes you are correct, obviously. My point is that the reference to the java
documentation led me to conclude erroneously that the pattern would be
interpreted as a java string literal, requiring the double-escape.
Clarifying this is not the case would eliminate any confusion. For
example:
pattern - Java regular expression pattern to match; NULL means no match is
attempted; The pattern is not interpreted as a String literal, therefore
double-escaping (e.g., \\s, \\w) is not required.
You might want to send a PR for such change, the file is
https://github.com/apache/syncope/blob/2_0_X/src/main/asciidoc/reference-guide/concepts/policies.adoc
If you're willing to contribute, I invite you to submit an ICLA:
http://syncope.apache.org/contributing.html#How_do_I_become_a_contributor_or_a_committer
I obviously know it now, so it isn't an issue for me anymore.
Grazie, as always, for your attention, tremendous effort, and awesome
product.
It's our pleasure :-)
Regards.
On Tue, Apr 17, 2018 at 11:30 AM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:
On 17/04/2018 17:25, varontron wrote:
Hi,
In configuring an Account policy, I included a pattern conformity
requirement.
[\\w@\\-\\.]+
meaning all one word or a normal email address, and ok, hyphens too.
However, as you may have noticed, the double-backslashes confound the
pattern. It should instead be:
[\w@\-\.]+
This appeared to work as intended.
The Reference Guide states "pattern - Java regular expression pattern to
match; NULL means no match is attempted;"
I inferred from this that, like in java regex strings, double-backslashes
were required for special characters:
"The backslash character ('\') serves to introduce escaped constructs, as
defined in the table above, as well as to quote characters that otherwise
would be interpreted as unescaped constructs. Thus the expression \\
matches
a single backslash and \{ matches a left brace."
Perhaps the docs could clarify this?
Hi,
I don't think so: it's
[\\w@\\-\\.]+
when you use it inside a string literal in Java, but the actual regex is
always
[\w@\-\.]+
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/
--
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: Misleading policy documentation (minor)
Yes you are correct, obviously. My point is that the reference to the java
documentation led me to conclude erroneously that the pattern would be
interpreted as a java string literal, requiring the double-escape.
Clarifying this is not the case would eliminate any confusion. For
example:
pattern - Java regular expression pattern to match; NULL means no match is
attempted; The pattern is not interpreted as a String literal, therefore
double-escaping (e.g., \\s, \\w) is not required.
I obviously know it now, so it isn't an issue for me anymore.
Grazie, as always, for your attention, tremendous effort, and awesome
product.
Dave
On Tue, Apr 17, 2018 at 11:30 AM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:
> On 17/04/2018 17:25, varontron wrote:
>
>> Hi,
>>
>> In configuring an Account policy, I included a pattern conformity
>> requirement.
>>
>> [\\w@\\-\\.]+
>>
>> meaning all one word or a normal email address, and ok, hyphens too.
>>
>> However, as you may have noticed, the double-backslashes confound the
>> pattern. It should instead be:
>>
>> [\w@\-\.]+
>>
>> This appeared to work as intended.
>>
>> The Reference Guide states "pattern - Java regular expression pattern to
>> match; NULL means no match is attempted;"
>>
>> I inferred from this that, like in java regex strings, double-backslashes
>> were required for special characters:
>>
>> "The backslash character ('\') serves to introduce escaped constructs, as
>> defined in the table above, as well as to quote characters that otherwise
>> would be interpreted as unescaped constructs. Thus the expression \\
>> matches
>> a single backslash and \{ matches a left brace."
>>
>> Perhaps the docs could clarify this?
>>
>
> Hi,
> I don't think so: it's
>
> [\\w@\\-\\.]+
>
> when you use it inside a string literal in Java, but the actual regex is
> always
>
> [\w@\-\.]+
>
> 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/
>
>
Re: Dashboard exception - approvals
On 17/04/2018 17:39, varontron wrote: Hi, Yes I deployed the generated war files, thus I was able to update the default Activiti "User Workflow" with the approval form extensionElements as described in https://ci.apache.org/projects/syncope/2_0_X/reference-guide.html#approval Here's the trace (it's all wicket): It seems that at least one of the forms have a null key; to check, go to http://host:port/syncope/swagger then to UserWorkflow > GET click "Try out" then "Execute" and paste the response body. Regards. P.S. It's better to use the user ML for such e-mails: please use that for the future, thanks. -- 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
Hi, Yes I deployed the generated war files, thus I was able to update the default Activiti "User Workflow" with the approval form extensionElements as described in https://ci.apache.org/projects/syncope/2_0_X/reference-guide.html#approval Here's the trace (it's all wicket): 14:29:30.993 ERROR org.apache.syncope.client.console.SyncopeConsoleRequestCycleListener - Exception found org.apache.wicket.WicketRuntimeException: An error occurred while getting the model object for Component: [Component id = key, page = org.apache.syncope.client.console.pages.Dashboard, path = body:approvalsWidget:latestAlertsList:latestAlerts:0:alert:approval:key, type = org.apache.wicket.markup.html.basic.Label, isVisible = true, isVersioned = true, markup = [markup = jar:file:/var/lib/tomcat8/webapps/syncope-console/WEB-INF/lib/syncope-client-console-2.0.9-SNAPSHOT.jar!/org/apache/syncope/client/console/widgets/ApprovalsWidget$InnerPanel.html , index = 0, current = '' (line 0, column 0)]] at org.apache.wicket.Component.getDefaultModelObject(Component.java:1651) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1674) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.markup.html.basic.Label.onComponentTagBody(Label.java:115) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.markup.html.panel.DefaultMarkupSourcingStrategy.onComponentTagBody(DefaultMarkupSourcingStrategy.java:70) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.Component.internalRenderComponent(Component.java:2601) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.markup.html.WebComponent.onRender(WebComponent.java:60) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.Component.internalRender(Component.java:2401) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.Component.render(Component.java:2329) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1515) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.renderAll(MarkupContainer.java:1718) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:1693) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:1648) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.markup.html.link.AbstractLink.onComponentTagBody(AbstractLink.java:82) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.markup.html.panel.DefaultMarkupSourcingStrategy.onComponentTagBody(DefaultMarkupSourcingStrategy.java:70) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.Component.internalRenderComponent(Component.java:2601) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1657) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.Component.internalRender(Component.java:2401) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.Component.render(Component.java:2329) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1515) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.renderAll(MarkupContainer.java:1718) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:1693) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.renderAssociatedMarkup(MarkupContainer.java:799) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.markup.html.panel.AssociatedMarkupSourcingStrategy.renderAssociatedMarkup(AssociatedMarkupSourcingStrategy.java:77) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.markup.html.panel.PanelMarkupSourcingStrategy.onComponentTagBody(PanelMarkupSourcingStrategy.java:112) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.Component.internalRenderComponent(Component.java:2601) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1657) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.Component.internalRender(Component.java:2401) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.Component.render(Component.java:2329) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1515) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.renderAll(MarkupContainer.java:1718) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:1693) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:1648) ~[wicket-core-7.10.0.jar:7.10.0] at
Re: Misleading policy documentation (minor)
On 17/04/2018 17:25, varontron wrote:
Hi,
In configuring an Account policy, I included a pattern conformity
requirement.
[\\w@\\-\\.]+
meaning all one word or a normal email address, and ok, hyphens too.
However, as you may have noticed, the double-backslashes confound the
pattern. It should instead be:
[\w@\-\.]+
This appeared to work as intended.
The Reference Guide states "pattern - Java regular expression pattern to
match; NULL means no match is attempted;"
I inferred from this that, like in java regex strings, double-backslashes
were required for special characters:
"The backslash character ('\') serves to introduce escaped constructs, as
defined in the table above, as well as to quote characters that otherwise
would be interpreted as unescaped constructs. Thus the expression \\ matches
a single backslash and \{ matches a left brace."
Perhaps the docs could clarify this?
Hi,
I don't think so: it's
[\\w@\\-\\.]+
when you use it inside a string literal in Java, but the actual regex is
always
[\w@\-\.]+
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/
Re: Dashboard exception - approvals
Hi, approval can only work with Activiti or Flowable. When you say 'Re-deployed with '-P all' ', do you mean you deployed the generated WAR files after building with all parameters indicated in https://syncope.apache.org/docs/reference-guide.html#customization e.g. mvn -Pall clean verify \ -Dconf.directory=/opt/syncope/conf \ -Dbundles.directory=/opt/syncope/bundles \ -Dlog.directory=/opt/syncope/log ? Could you please attach the whole stacktrace from the console logs? Regards. On 17/04/2018 17:14, varontron wrote: Hi, Unable to load dashboard due to "Unable to find property: 'null' for component: body:approvalsWidget:latestAlertsList:latestAlerts:0:alert:approval:key..." Steps to reproduce: Deployed 2.0.9-SNAPSHOT Configured policies, realm, role Using default schemas (No resources, users, or groups created) Re-deployed with '-P all' Updated role with WORKFLOW entitlements (though no users assigned to role yet) Configured approval form in Activiti Approval User Task per Reference Guide Self-registered user with enduser ui Dashboard caused exception: Last cause: Unable to find property: 'null' for component: body:approvalsWidget:latestAlertsList:latestAlerts:0:alert:approval:key [class=org.apache.wicket.markup.html.basic.Label]. Locale: null, style: null WicketMessage: An error occurred while getting the model object for Component: [Component id = key, page = org.apache.syncope.client.console.pages.Dashboard, path = body:approvalsWidget:latestAlertsList:latestAlerts:0:alert:approval:key, type = org.apache.wicket.markup.html.basic.Label, isVisible = true, isVersioned = true, markup = [markup = jar:file:/var/lib/tomcat8/webapps/syncope-console/WEB-INF/lib/syncope-client-console-2.0.9-SNAPSHOT.jar!/org/apache/syncope/client/console/widgets/ApprovalsWidget$InnerPanel.html , index = 0, current = '' (line 0, column 0)]] Did I leave out a config step? Is this resolvable without dropping the db? Is it possible to catch the exception so as not to break the dashboard? Thanks, Dave - http://analgesicsolutions.com https://github.com/Novartis/YADA -- Sent from: http://syncope-dev.1063484.n5.nabble.com/ -- 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/
Misleading policy documentation (minor)
Hi,
In configuring an Account policy, I included a pattern conformity
requirement.
[\\w@\\-\\.]+
meaning all one word or a normal email address, and ok, hyphens too.
However, as you may have noticed, the double-backslashes confound the
pattern. It should instead be:
[\w@\-\.]+
This appeared to work as intended.
The Reference Guide states "pattern - Java regular expression pattern to
match; NULL means no match is attempted;"
I inferred from this that, like in java regex strings, double-backslashes
were required for special characters:
"The backslash character ('\') serves to introduce escaped constructs, as
defined in the table above, as well as to quote characters that otherwise
would be interpreted as unescaped constructs. Thus the expression \\ matches
a single backslash and \{ matches a left brace."
Perhaps the docs could clarify this?
Cheers,
Dave
-
http://analgesicsolutions.com
https://github.com/Novartis/YADA
--
Sent from: http://syncope-dev.1063484.n5.nabble.com/
Dashboard exception - approvals
Hi, Unable to load dashboard due to "Unable to find property: 'null' for component: body:approvalsWidget:latestAlertsList:latestAlerts:0:alert:approval:key..." Steps to reproduce: Deployed 2.0.9-SNAPSHOT Configured policies, realm, role Using default schemas (No resources, users, or groups created) Re-deployed with '-P all' Updated role with WORKFLOW entitlements (though no users assigned to role yet) Configured approval form in Activiti Approval User Task per Reference Guide Self-registered user with enduser ui Dashboard caused exception: Last cause: Unable to find property: 'null' for component: body:approvalsWidget:latestAlertsList:latestAlerts:0:alert:approval:key [class=org.apache.wicket.markup.html.basic.Label]. Locale: null, style: null WicketMessage: An error occurred while getting the model object for Component: [Component id = key, page = org.apache.syncope.client.console.pages.Dashboard, path = body:approvalsWidget:latestAlertsList:latestAlerts:0:alert:approval:key, type = org.apache.wicket.markup.html.basic.Label, isVisible = true, isVersioned = true, markup = [markup = jar:file:/var/lib/tomcat8/webapps/syncope-console/WEB-INF/lib/syncope-client-console-2.0.9-SNAPSHOT.jar!/org/apache/syncope/client/console/widgets/ApprovalsWidget$InnerPanel.html , index = 0, current = '' (line 0, column 0)]] Did I leave out a config step? Is this resolvable without dropping the db? Is it possible to catch the exception so as not to break the dashboard? Thanks, Dave - http://analgesicsolutions.com https://github.com/Novartis/YADA -- Sent from: http://syncope-dev.1063484.n5.nabble.com/
[jira] [Resolved] (SYNCOPE-1299) Manual reconciliation
[ https://issues.apache.org/jira/browse/SYNCOPE-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1299. - Resolution: Fixed > 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=16440988#comment-16440988 ] ASF subversion and git services commented on SYNCOPE-1299: -- Commit a660a26b5c1fd4198009f08535ec437e80cf86e3 in syncope's branch refs/heads/2_0_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=a660a26 ] [SYNCOPE-1299] Console features implemented > 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=16440989#comment-16440989 ] ASF subversion and git services commented on SYNCOPE-1299: -- Commit 4da5dcccbf69acd7a706cfffe3db8f1c4494eac5 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=4da5dcc ] [SYNCOPE-1299] Console features implemented > 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)
