[jira] [Resolved] (SYNCOPE-1294) Plainschema panel doesn't display the assigned validator class

[Marco Di Sabatino Di Diodoro (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marco Di Sabatino Di Diodoro resolved SYNCOPE-1294.
---
Resolution: Fixed

> Plainschema panel doesn't display the assigned validator class
> --
>
> Key: SYNCOPE-1294
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1294
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.8, 2.1.0
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
>Priority: Major
> Fix For: 2.0.9, 2.1.0
>
>
> If a plain schema has assigned a validator class, the console always shows a 
> null value



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SYNCOPE-1294) Plainschema panel doesn't display the assigned validator class

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425748#comment-16425748
 ] 

ASF subversion and git services commented on SYNCOPE-1294:
--

Commit 38327a0a23ab3b9869bf65cbcdbc230aa0a0c00c in syncope's branch 
refs/heads/2_0_X from [~mdisabatino]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=38327a0 ]

[SYNCOPE-1294] PlainSchemaDetailsPanel doesn't display the assigned validator 
class


> Plainschema panel doesn't display the assigned validator class
> --
>
> Key: SYNCOPE-1294
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1294
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.8, 2.1.0
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
>Priority: Major
> Fix For: 2.0.9, 2.1.0
>
>
> If a plain schema has assigned a validator class, the console always shows a 
> null value



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SYNCOPE-1294) Plainschema panel doesn't display the assigned validator class

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425747#comment-16425747
 ] 

ASF subversion and git services commented on SYNCOPE-1294:
--

Commit 95ee2ffe810336f3bf785e2d231fa15e71630919 in syncope's branch 
refs/heads/master from [~mdisabatino]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=95ee2ff ]

[SYNCOPE-1294] PlainSchemaDetailsPanel doesn't display the assigned validator 
class


> Plainschema panel doesn't display the assigned validator class
> --
>
> Key: SYNCOPE-1294
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1294
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.8, 2.1.0
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
>Priority: Major
> Fix For: 2.0.9, 2.1.0
>
>
> If a plain schema has assigned a validator class, the console always shows a 
> null value



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: SYNCOPE-1270 : OpenID Connect client feature

[Isuranga Perera]

Hi Francesco,

Sure I'll submit the ICLA. I'll start a separate thread for the project
discussions.

Best Regards

On Wed, Apr 4, 2018 at 9:05 PM, Francesco Chicchiriccò 
wrote:

> On 04/04/2018 16:07, Isuranga Perera wrote:
>
>> Hi,
>>
>> I would like to work on SYNCOPE-1219. But it has GSoC 2018 tag. So is it
>> okay to work on that.
>>
>
> SYNCOPE-1219 has received no proposals for GSoC.
> Feature-wise, it's exactly as SYNCOPE-1220 (which is for Netbeans,
> instead).
>
> It would be great if you can review the current Eclipse plugin, polish if
> needed and add support for Groovy implementations.
>
> In the meanwhile, you might want to do some paperwork:
>
> http://syncope.apache.org/contributing.html#How_do_I_become_
> a_contributor_or_a_committer
>
> by sending your ICLA.
>
> Finally, consider that Groovy implementations are only available in the
> master branch, so you should work there.
>
> Regards.
>
> On Wed, Apr 4, 2018 at 4:47 PM, Francesco Chicchiriccò <
>> ilgro...@apache.org > wrote:
>>
>> Hi,
>> I can see a couple of issues in JIRA waiting for someone to pick up:
>>
>> * https://issues.apache.org/jira/browse/SYNCOPE-1019
>> 
>> * https://issues.apache.org/jira/browse/SYNCOPE-1219
>> 
>>
>> Unfortunately, none is related to the competences mentioned below,
>> but maybe you can take them into account.
>>
>> Regards.
>>
>> On 04/04/2018 09:27, Isuranga Perera wrote:
>>
>> Hi Francesco,
>>
>> Can you suggest a feature I can work on. I've previously
>> worked in OpenID Connect, SAML, SCIM and XACML projects. So
>> appreciate if you can suggest a feature/issue that I can work on.
>>
>> Best Regards
>> Isuranga Perera
>>
>> On Tue, Apr 3, 2018 at 4:31 PM, Dima Ayash
>> 
>> >>
>>
>> wrote:
>>
>> Dear,
>>
>> Thank you for your interest.
>> The work has been done until now regarding this feature is:
>> •The authorization code flow is the flow that is used for and
>> "Google" as an example for the OpenID Provider.
>> •To configure the OpenID Provider metadata to apply this flow,
>> there are two ways depends on what the OpenID Provider
>> supports,
>> in case of supporting the Discovery  Document, requesting this
>> document and process the response and stored the required
>> values
>> otherwise the user needs to insert these values.
>> •The work used CXF OIDC dependency, and took benefits from the
>> structure of SAML2.0 feature.
>> •The work is still under progress, the core and the logic
>> of the
>> flow is done and tested, the user can have a session by
>> logging
>> successfully to his account in "Google" and by having a
>> user in
>> Apache Syncope.
>>
>> I would really appreciate questions for more details and
>> also more
>> suggestions to enhance this work.
>>
>> Thank you in advance and best regards,
>> Dima Ayash.
>>
>> - Original Message -
>> From: "Francesco Chicchiriccò" > 
>> >>
>> To: dev@syncope.apache.org 
>> >
>> Sent: Tuesday, April 3, 2018 8:54:00 AM
>> Subject: Re: SYNCOPE-1270 : OpenID Connect client feature
>>
>> On 03/04/2018 06:39, Isuranga Perera wrote:
>> > Hi All,
>> >
>> > I would like to contribute $subject. I have contributed
>> to WSO2
>> Identity
>> > server and have worked with OpenID Connect and its profiles.
>> Appreciate if
>> > someone can provide me guidance throughout this feature.
>> >
>> > Best Regards
>> > Isuranga Perera
>>
>> Dear Isuranga,
>> thanks for your interest in Apache Syncope.
>>
>> As far as we know, there is already someone at work on the
>> topic: see
>>
>> https://lists.apache.org/thread.html/d36e9354a4a638c7afc76a3
>> e6d69aaf24d7c4e2c6a377e2ccfefcabe@%3Cdev.syncope.apache.org%3E
>> > 3e6d69aaf24d7c4e2c6a377e2ccfefcabe@%3Cdev.syncope.apache.org%3E>
>>
>> > 

Re: SYNCOPE-1270 : OpenID Connect client feature

[Francesco Chicchiriccò]

On 04/04/2018 16:07, Isuranga Perera wrote:

Hi,

I would like to work on SYNCOPE-1219. But it has GSoC 2018 tag. So is 
it okay to work on that.


SYNCOPE-1219 has received no proposals for GSoC.
Feature-wise, it's exactly as SYNCOPE-1220 (which is for Netbeans, instead).

It would be great if you can review the current Eclipse plugin, polish 
if needed and add support for Groovy implementations.


In the meanwhile, you might want to do some paperwork:

http://syncope.apache.org/contributing.html#How_do_I_become_a_contributor_or_a_committer

by sending your ICLA.

Finally, consider that Groovy implementations are only available in the 
master branch, so you should work there.


Regards.

On Wed, Apr 4, 2018 at 4:47 PM, Francesco Chicchiriccò 
> wrote:


Hi,
I can see a couple of issues in JIRA waiting for someone to pick up:

* https://issues.apache.org/jira/browse/SYNCOPE-1019

* https://issues.apache.org/jira/browse/SYNCOPE-1219


Unfortunately, none is related to the competences mentioned below,
but maybe you can take them into account.

Regards.

On 04/04/2018 09:27, Isuranga Perera wrote:

Hi Francesco,

Can you suggest a feature I can work on. I've previously
worked in OpenID Connect, SAML, SCIM and XACML projects. So
appreciate if you can suggest a feature/issue that I can work on.

Best Regards
Isuranga Perera

On Tue, Apr 3, 2018 at 4:31 PM, Dima Ayash

>>
wrote:

    Dear,

    Thank you for your interest.
    The work has been done until now regarding this feature is:
    •The authorization code flow is the flow that is used for and
    "Google" as an example for the OpenID Provider.
    •To configure the OpenID Provider metadata to apply this flow,
    there are two ways depends on what the OpenID Provider
supports,
    in case of supporting the Discovery  Document, requesting this
    document and process the response and stored the required
values
    otherwise the user needs to insert these values.
    •The work used CXF OIDC dependency, and took benefits from the
    structure of SAML2.0 feature.
    •The work is still under progress, the core and the logic
of the
    flow is done and tested, the user can have a session by
logging
    successfully to his account in "Google" and by having a
user in
    Apache Syncope.

    I would really appreciate questions for more details and
also more
    suggestions to enhance this work.

    Thank you in advance and best regards,
    Dima Ayash.

    - Original Message -
    From: "Francesco Chicchiriccò" 
    >>
    To: dev@syncope.apache.org 
>
    Sent: Tuesday, April 3, 2018 8:54:00 AM
    Subject: Re: SYNCOPE-1270 : OpenID Connect client feature

    On 03/04/2018 06:39, Isuranga Perera wrote:
    > Hi All,
    >
    > I would like to contribute $subject. I have contributed
to WSO2
    Identity
    > server and have worked with OpenID Connect and its profiles.
    Appreciate if
    > someone can provide me guidance throughout this feature.
    >
    > Best Regards
    > Isuranga Perera

    Dear Isuranga,
    thanks for your interest in Apache Syncope.

    As far as we know, there is already someone at work on the
topic: see


https://lists.apache.org/thread.html/d36e9354a4a638c7afc76a3e6d69aaf24d7c4e2c6a377e2ccfefcabe@%3Cdev.syncope.apache.org%3E


   

>

    Maybe you can pick one of the other feature requests from
JIRA, or
    propose a new one.

    @Dima: could it be possible to provide a status update
about your work
    there?

    Regards.


--
Francesco Chicchiriccò

Tirasa - Open Source Excellence

[jira] [Resolved] (SYNCOPE-1287) Remediation

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò resolved SYNCOPE-1287.
-
Resolution: Fixed

> Remediation
> ---
>
> Key: SYNCOPE-1287
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1287
> Project: Syncope
>  Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.1.0
>
>
> Errors during pull might arise for various reasons: for example, values are 
> not provided for all mandatory attributes, or values are failing the 
> configured validation.
> Currently, if an entity (User, Group or Any Object) is failing during a Pull 
> Task execution, it is simply reported as an error, and logged as execution 
> result.
> As a new feature, administrators could be given the chance to perform 
> _remediation_ on the failing entities, in a similar fashion they do with 
> approval forms.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SYNCOPE-1294) Plainschema panel doesn't display the assigned validator class

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-1294:

Fix Version/s: 2.1.0

> Plainschema panel doesn't display the assigned validator class
> --
>
> Key: SYNCOPE-1294
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1294
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.8, 2.1.0
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
>Priority: Major
> Fix For: 2.0.9, 2.1.0
>
>
> If a plain schema has assigned a validator class, the console always shows a 
> null value



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SYNCOPE-1287) Remediation

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425720#comment-16425720
 ] 

ASF subversion and git services commented on SYNCOPE-1287:
--

Commit 0bc714db0c8ce5a68708d49ac1796ad6d21c3a25 in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=0bc714d ]

[SYNCOPE-1287] Documentation


> Remediation
> ---
>
> Key: SYNCOPE-1287
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1287
> Project: Syncope
>  Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.1.0
>
>
> Errors during pull might arise for various reasons: for example, values are 
> not provided for all mandatory attributes, or values are failing the 
> configured validation.
> Currently, if an entity (User, Group or Any Object) is failing during a Pull 
> Task execution, it is simply reported as an error, and logged as execution 
> result.
> As a new feature, administrators could be given the chance to perform 
> _remediation_ on the failing entities, in a similar fashion they do with 
> approval forms.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SYNCOPE-1294) Plainschema panel doesn't display the assigned validator class

[Marco Di Sabatino Di Diodoro (JIRA)]

Marco Di Sabatino Di Diodoro created SYNCOPE-1294:
-

 Summary: Plainschema panel doesn't display the assigned validator 
class
 Key: SYNCOPE-1294
 URL: https://issues.apache.org/jira/browse/SYNCOPE-1294
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 2.0.8, 2.1.0
Reporter: Marco Di Sabatino Di Diodoro
Assignee: Marco Di Sabatino Di Diodoro
 Fix For: 2.0.9


If a plain schema has assigned a validator class, the console always shows a 
null value



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: 2.0.8 (stable) YAMLFactory not found et al

[varontron]

Hi,

Thanks for your feedback.  I can confirm the YAML jar issue is resolved in
2.0.9-SNAPSHOT.

-
http://analgesicsolutions.com
https://github.com/Novartis/YADA

--
Sent from: http://syncope-dev.1063484.n5.nabble.com/

[jira] [Commented] (SYNCOPE-1287) Remediation

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425659#comment-16425659
 ] 

ASF subversion and git services commented on SYNCOPE-1287:
--

Commit 4e781f4a7457248e5e1566a1ca35dbcf5f139287 in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=4e781f4 ]

[SYNCOPE-1287] Console implementation


> Remediation
> ---
>
> Key: SYNCOPE-1287
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1287
> Project: Syncope
>  Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.1.0
>
>
> Errors during pull might arise for various reasons: for example, values are 
> not provided for all mandatory attributes, or values are failing the 
> configured validation.
> Currently, if an entity (User, Group or Any Object) is failing during a Pull 
> Task execution, it is simply reported as an error, and logged as execution 
> result.
> As a new feature, administrators could be given the chance to perform 
> _remediation_ on the failing entities, in a similar fashion they do with 
> approval forms.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: quartz tables not installing

[varontron]

Hi,

I experienced the same issue with a new build of 2.0.9-SNAPSHOT and it
occurred to me the difference might be this, on line 19 of
core/src/main/resources/domains/Master.properties:

Master.schema=syncope

and in $TOMCAT_HOME/conf/context.xml in the Resource config I have included
the attribute: 

currentSchema="syncope"

i.e., I am not using the 'public' schema.  

Perhaps this is a factor.

Dave

-
http://analgesicsolutions.com
https://github.com/Novartis/YADA

--
Sent from: http://syncope-dev.1063484.n5.nabble.com/

Re: SYNCOPE-1270 : OpenID Connect client feature

[Isuranga Perera]

Hi,

I would like to work on SYNCOPE-1219. But it has GSoC 2018 tag. So is it
okay to work on that.

Best Regards

On Wed, Apr 4, 2018 at 4:47 PM, Francesco Chicchiriccò 
wrote:

> Hi,
> I can see a couple of issues in JIRA waiting for someone to pick up:
>
> * https://issues.apache.org/jira/browse/SYNCOPE-1019
> * https://issues.apache.org/jira/browse/SYNCOPE-1219
>
> Unfortunately, none is related to the competences mentioned below, but
> maybe you can take them into account.
>
> Regards.
>
> On 04/04/2018 09:27, Isuranga Perera wrote:
>
>> Hi Francesco,
>>
>> Can you suggest a feature I can work on. I've previously worked in OpenID
>> Connect, SAML, SCIM and XACML projects. So appreciate if you can suggest a
>> feature/issue that I can work on.
>>
>> Best Regards
>> Isuranga Perera
>>
>> On Tue, Apr 3, 2018 at 4:31 PM, Dima Ayash > > wrote:
>>
>> Dear,
>>
>> Thank you for your interest.
>> The work has been done until now regarding this feature is:
>> •The authorization code flow is the flow that is used for and
>> "Google" as an example for the OpenID Provider.
>> •To configure the OpenID Provider metadata to apply this flow,
>> there are two ways depends on what the OpenID Provider supports,
>> in case of supporting the Discovery  Document, requesting this
>> document and process the response and stored the required values
>> otherwise the user needs to insert these values.
>> •The work used CXF OIDC dependency, and took benefits from the
>> structure of SAML2.0 feature.
>> •The work is still under progress, the core and the logic of the
>> flow is done and tested, the user can have a session by logging
>> successfully to his account in "Google" and by having a user in
>> Apache Syncope.
>>
>> I would really appreciate questions for more details and also more
>> suggestions to enhance this work.
>>
>> Thank you in advance and best regards,
>> Dima Ayash.
>>
>> - Original Message -
>> From: "Francesco Chicchiriccò" > >
>> To: dev@syncope.apache.org 
>> Sent: Tuesday, April 3, 2018 8:54:00 AM
>> Subject: Re: SYNCOPE-1270 : OpenID Connect client feature
>>
>> On 03/04/2018 06:39, Isuranga Perera wrote:
>> > Hi All,
>> >
>> > I would like to contribute $subject. I have contributed to WSO2
>> Identity
>> > server and have worked with OpenID Connect and its profiles.
>> Appreciate if
>> > someone can provide me guidance throughout this feature.
>> >
>> > Best Regards
>> > Isuranga Perera
>>
>> Dear Isuranga,
>> thanks for your interest in Apache Syncope.
>>
>> As far as we know, there is already someone at work on the topic: see
>>
>> https://lists.apache.org/thread.html/d36e9354a4a638c7afc76a3
>> e6d69aaf24d7c4e2c6a377e2ccfefcabe@%3Cdev.syncope.apache.org%3E
>> > 3e6d69aaf24d7c4e2c6a377e2ccfefcabe@%3Cdev.syncope.apache.org%3E>
>>
>> Maybe you can pick one of the other feature requests from JIRA, or
>> propose a new one.
>>
>> @Dima: could it be possible to provide a status update about your work
>> there?
>>
>> 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] [Updated] (SYNCOPE-1293) Make "token" field searchable again

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-1293:

Description: 
Reset password notification may contain "about" value with a "filter" property.
 And "token" field of a "UserTO" may be used in a fiql query of password reset 
notification.
 E.g. {{token!=$null}} query can be used as a filter value JPAAnyAbout entity 
which is a part of JPANotification entity.

If token field is not searchable for UserTO object, then 
SearchCondVisitor#createAttributeCond(final String schema) creates 
AttributeCond object instead of AnyCond object, and therefore 
NotificationManagerImpl skips password reset notification and doesn't process 
it correctly (look at 
[NotificationManagerImpl|https://github.com/apache/syncope/blob/master/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/notification/NotificationManagerImpl.java#L344]).

  was:
Reset password notification may contain "about" value with a "filter" property.
 And "token" field of a "UserTO" may be used in a fiql query of password reset 
notification.
 E.g. {{token!=$null}} query can be used as a filter value JPAAnyAbout entity 
which is a part of JPANotification entity.

If token field is not searchable for UserTO object, then 
SearchCondVisitor#createAttributeCond(final String schema) creates 
AttributeCond object instead of AnyCond object, and therefore 
NotificationManagerImpl skips password reset notification and doesn't process 
it correctly (look at line 344 in 
[https://github.com/apache/syncope/blob/master/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/notification/NotificationManagerImpl.java]).

Link to conversation in git:
 
[https://github.com/apache/syncope/commit/7b168c142b09c3b03e39f1449211e7ddf026a14d]


> Make "token" field searchable again
> ---
>
> Key: SYNCOPE-1293
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1293
> Project: Syncope
>  Issue Type: Bug
>  Components: common
>Affects Versions: 2.0.8
>Reporter: DmitriyB.
>Priority: Minor
> Fix For: 2.0.9, 2.1.0
>
>
> Reset password notification may contain "about" value with a "filter" 
> property.
>  And "token" field of a "UserTO" may be used in a fiql query of password 
> reset notification.
>  E.g. {{token!=$null}} query can be used as a filter value JPAAnyAbout entity 
> which is a part of JPANotification entity.
> If token field is not searchable for UserTO object, then 
> SearchCondVisitor#createAttributeCond(final String schema) creates 
> AttributeCond object instead of AnyCond object, and therefore 
> NotificationManagerImpl skips password reset notification and doesn't process 
> it correctly (look at 
> [NotificationManagerImpl|https://github.com/apache/syncope/blob/master/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/notification/NotificationManagerImpl.java#L344]).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SYNCOPE-1293) Default password reset notifications not working

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-1293:

Summary: Default password reset notifications not working  (was: Make 
"token" field searchable again)

> Default password reset notifications not working
> 
>
> Key: SYNCOPE-1293
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1293
> Project: Syncope
>  Issue Type: Bug
>  Components: common
>Affects Versions: 2.0.8
>Reporter: DmitriyB.
>Priority: Minor
> Fix For: 2.0.9, 2.1.0
>
>
> Reset password notification may contain "about" value with a "filter" 
> property.
>  And "token" field of a "UserTO" may be used in a fiql query of password 
> reset notification.
>  E.g. {{token!=$null}} query can be used as a filter value JPAAnyAbout entity 
> which is a part of JPANotification entity.
> If token field is not searchable for UserTO object, then 
> SearchCondVisitor#createAttributeCond(final String schema) creates 
> AttributeCond object instead of AnyCond object, and therefore 
> NotificationManagerImpl skips password reset notification and doesn't process 
> it correctly (look at 
> [NotificationManagerImpl|https://github.com/apache/syncope/blob/master/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/notification/NotificationManagerImpl.java#L344]).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SYNCOPE-1293) Make "token" field searchable again

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-1293:

Fix Version/s: 2.1.0
   2.0.9

> Make "token" field searchable again
> ---
>
> Key: SYNCOPE-1293
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1293
> Project: Syncope
>  Issue Type: Bug
>  Components: common
>Affects Versions: 2.0.8
>Reporter: DmitriyB.
>Priority: Minor
> Fix For: 2.0.9, 2.1.0
>
>
> Reset password notification may contain "about" value with a "filter" 
> property.
>  And "token" field of a "UserTO" may be used in a fiql query of password 
> reset notification.
>  E.g. {{token!=$null}} query can be used as a filter value JPAAnyAbout entity 
> which is a part of JPANotification entity.
> If token field is not searchable for UserTO object, then 
> SearchCondVisitor#createAttributeCond(final String schema) creates 
> AttributeCond object instead of AnyCond object, and therefore 
> NotificationManagerImpl skips password reset notification and doesn't process 
> it correctly (look at line 344 in 
> [https://github.com/apache/syncope/blob/master/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/notification/NotificationManagerImpl.java]).
> Link to conversation in git:
>  
> [https://github.com/apache/syncope/commit/7b168c142b09c3b03e39f1449211e7ddf026a14d]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SYNCOPE-1293) Make "token" field searchable again

[DmitriyB. (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

DmitriyB. updated SYNCOPE-1293:
---
Description: 
Reset password notification may contain "about" value with a "filter" property.
 And "token" field of a "UserTO" may be used in a fiql query of password reset 
notification.
 E.g. {{token!=$null}} query can be used as a filter value JPAAnyAbout entity 
which is a part of JPANotification entity.

If token field is not searchable for UserTO object, then 
SearchCondVisitor#createAttributeCond(final String schema) creates 
AttributeCond object instead of AnyCond object, and therefore 
NotificationManagerImpl skips password reset notification and doesn't process 
it correctly (look at line 344 in 
[https://github.com/apache/syncope/blob/master/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/notification/NotificationManagerImpl.java]).

Link to conversation in git:
 
[https://github.com/apache/syncope/commit/7b168c142b09c3b03e39f1449211e7ddf026a14d]

  was:
Reset password notification may contain "about" value with a "filter" property.
And "token" field of a "UserTO" may be used in a fiql query of password
reset notification.
E.g. {{token!=$null}} query can be used as a filter value JPAAnyAbout entity 
which is a part of JPANotification entity.

If token field is not searchable for UserTO object, then 
SearchCondVisitor#createAttributeCond(final String schema) creates 
AttributeCond object instead of AnyCond object, and therefore 
NotificationManagerImpl skips password reset notification and doesn't process 
it correctly (look at line 344 in 
[https://github.com/apache/syncope/blob/master/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/notification/NotificationManagerImpl.java]).

 

 

Link to conversation in git:
https://github.com/apache/syncope/commit/7b168c142b09c3b03e39f1449211e7ddf026a14d


> Make "token" field searchable again
> ---
>
> Key: SYNCOPE-1293
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1293
> Project: Syncope
>  Issue Type: Bug
>  Components: common
>Affects Versions: 2.0.8
>Reporter: DmitriyB.
>Priority: Minor
> Fix For: 2.0.9, 2.1.0
>
>
> Reset password notification may contain "about" value with a "filter" 
> property.
>  And "token" field of a "UserTO" may be used in a fiql query of password 
> reset notification.
>  E.g. {{token!=$null}} query can be used as a filter value JPAAnyAbout entity 
> which is a part of JPANotification entity.
> If token field is not searchable for UserTO object, then 
> SearchCondVisitor#createAttributeCond(final String schema) creates 
> AttributeCond object instead of AnyCond object, and therefore 
> NotificationManagerImpl skips password reset notification and doesn't process 
> it correctly (look at line 344 in 
> [https://github.com/apache/syncope/blob/master/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/notification/NotificationManagerImpl.java]).
> Link to conversation in git:
>  
> [https://github.com/apache/syncope/commit/7b168c142b09c3b03e39f1449211e7ddf026a14d]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SYNCOPE-1293) Make "token" field searchable again

[DmitriyB. (JIRA)]

DmitriyB. created SYNCOPE-1293:
--

 Summary: Make "token" field searchable again
 Key: SYNCOPE-1293
 URL: https://issues.apache.org/jira/browse/SYNCOPE-1293
 Project: Syncope
  Issue Type: Bug
  Components: common
Affects Versions: 2.0.8
Reporter: DmitriyB.


Reset password notification may contain "about" value with a "filter" property.
And "token" field of a "UserTO" may be used in a fiql query of password
reset notification.
E.g. {{token!=$null}} query can be used as a filter value JPAAnyAbout entity 
which is a part of JPANotification entity.

If token field is not searchable for UserTO object, then 
SearchCondVisitor#createAttributeCond(final String schema) creates 
AttributeCond object instead of AnyCond object, and therefore 
NotificationManagerImpl skips password reset notification and doesn't process 
it correctly (look at line 344 in 
[https://github.com/apache/syncope/blob/master/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/notification/NotificationManagerImpl.java]).

 

 

Link to conversation in git:
https://github.com/apache/syncope/commit/7b168c142b09c3b03e39f1449211e7ddf026a14d



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] syncope pull request #:

[ilgrosso]

Github user ilgrosso commented on the pull request:


https://github.com/apache/syncope/commit/7b168c142b09c3b03e39f1449211e7ddf026a14d#commitcomment-28411553
  
In 
common/lib/src/main/java/org/apache/syncope/common/lib/search/SearchableFields.java:
In 
common/lib/src/main/java/org/apache/syncope/common/lib/search/SearchableFields.java
 on line 39:
@Dmitriy333 I see your point; maybe we can explicitly allow the sole 
`token!=$null` FIQL condition.
Please open an issue on JIRA and possibly provide a PR to fix that, thanks!


---

[GitHub] syncope pull request #:

[Dmitriy333]

Github user Dmitriy333 commented on the pull request:


https://github.com/apache/syncope/commit/7b168c142b09c3b03e39f1449211e7ddf026a14d#commitcomment-28411382
  
In 
common/lib/src/main/java/org/apache/syncope/common/lib/search/SearchableFields.java:
In 
common/lib/src/main/java/org/apache/syncope/common/lib/search/SearchableFields.java
 on line 39:
@ilgrosso , Seems, that it would be great to make `token` field searchable 
again.

Reset password notification may contain "about" value with a "filter" 
property.
And "token" field of a "UserTO" may be used in a fiql query of password 
reset notification. 
E.g. `token!=$null` query can be used as a filter value JPAAnyAbout entity 
which is a part of  JPANotification entity.

If token field is not searchable for UserTO object, then 
SearchCondVisitor#createAttributeCond(final String schema) creates 
AttributeCond object instead of AnyCond object, and therefore 
NotificationManagerImpl skips password reset notification and doesn't process 
it correctly (look at line 344 in 
https://github.com/apache/syncope/blob/master/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/notification/NotificationManagerImpl.java).

FYI, I'm using release version 2.0.8


---

Re: SYNCOPE-1270 : OpenID Connect client feature

[Francesco Chicchiriccò]

Hi,
I can see a couple of issues in JIRA waiting for someone to pick up:

* https://issues.apache.org/jira/browse/SYNCOPE-1019
* https://issues.apache.org/jira/browse/SYNCOPE-1219

Unfortunately, none is related to the competences mentioned below, but 
maybe you can take them into account.


Regards.

On 04/04/2018 09:27, Isuranga Perera wrote:

Hi Francesco,

Can you suggest a feature I can work on. I've previously worked in 
OpenID Connect, SAML, SCIM and XACML projects. So appreciate if you 
can suggest a feature/issue that I can work on.


Best Regards
Isuranga Perera

On Tue, Apr 3, 2018 at 4:31 PM, Dima Ayash > wrote:


Dear,

Thank you for your interest.
The work has been done until now regarding this feature is:
•The authorization code flow is the flow that is used for and
"Google" as an example for the OpenID Provider.
•To configure the OpenID Provider metadata to apply this flow,
there are two ways depends on what the OpenID Provider supports,
in case of supporting the Discovery  Document, requesting this
document and process the response and stored the required values
otherwise the user needs to insert these values.
•The work used CXF OIDC dependency, and took benefits from the
structure of SAML2.0 feature.
•The work is still under progress, the core and the logic of the
flow is done and tested, the user can have a session by logging
successfully to his account in "Google" and by having a user in
Apache Syncope.

I would really appreciate questions for more details and also more
suggestions to enhance this work.

Thank you in advance and best regards,
Dima Ayash.

- Original Message -
From: "Francesco Chicchiriccò" >
To: dev@syncope.apache.org 
Sent: Tuesday, April 3, 2018 8:54:00 AM
Subject: Re: SYNCOPE-1270 : OpenID Connect client feature

On 03/04/2018 06:39, Isuranga Perera wrote:
> Hi All,
>
> I would like to contribute $subject. I have contributed to WSO2
Identity
> server and have worked with OpenID Connect and its profiles.
Appreciate if
> someone can provide me guidance throughout this feature.
>
> Best Regards
> Isuranga Perera

Dear Isuranga,
thanks for your interest in Apache Syncope.

As far as we know, there is already someone at work on the topic: see


https://lists.apache.org/thread.html/d36e9354a4a638c7afc76a3e6d69aaf24d7c4e2c6a377e2ccfefcabe@%3Cdev.syncope.apache.org%3E



Maybe you can pick one of the other feature requests from JIRA, or
propose a new one.

@Dima: could it be possible to provide a status update about your work
there?

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] [Closed] (SYNCOPE-1056) Installation of Apache Syncope - Archetype creation...

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò closed SYNCOPE-1056.
---
Resolution: Cannot Reproduce

> Installation of Apache Syncope - Archetype creation...
> --
>
> Key: SYNCOPE-1056
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1056
> Project: Syncope
>  Issue Type: Bug
>  Components: installer
>Affects Versions: 2.0.2
> Environment: Windows Server 2012 R2
> - Java jdk1.8.0_121
> - Apache maven 3.3.9
> - TomCat 8.5
> - MySQL
>Reporter: Heino Pasi
>Priority: Trivial
> Attachments: Syncope_Installation_Failure.JPG
>
>
> Running Syncope 2.0.2. GUI Installation I've got this error all the time. I 
> have tested with Java JDK 7.xx versions no matters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SYNCOPE-1292) Use Remote Key during Pull to match internal entities

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò resolved SYNCOPE-1292.
-
Resolution: Fixed

> Use Remote Key during Pull to match internal entities
> -
>
> Key: SYNCOPE-1292
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1292
> Project: Syncope
>  Issue Type: Improvement
>  Components: core
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.0.9, 2.1.0
>
>
> Following SYNCOPE-1182, extend the same approach to internal entities 
> matching during Pull, e.g. do not use {{__UID__}} but rather the value for 
> the attribute flagged as {{Remote Key}} in the Mapping.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SYNCOPE-1292) Use Remote Key during Pull to match internal entities

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425221#comment-16425221
 ] 

ASF subversion and git services commented on SYNCOPE-1292:
--

Commit 385b062f8da6c49537e3b97faf538758e0b77915 in syncope's branch 
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=385b062 ]

[SYNCOPE-1292] Implementation provided


> Use Remote Key during Pull to match internal entities
> -
>
> Key: SYNCOPE-1292
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1292
> Project: Syncope
>  Issue Type: Improvement
>  Components: core
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.0.9, 2.1.0
>
>
> Following SYNCOPE-1182, extend the same approach to internal entities 
> matching during Pull, e.g. do not use {{__UID__}} but rather the value for 
> the attribute flagged as {{Remote Key}} in the Mapping.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SYNCOPE-1292) Use Remote Key during Pull to match internal entities

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425222#comment-16425222
 ] 

ASF subversion and git services commented on SYNCOPE-1292:
--

Commit f171ed2aeb6de42a5f0f2430d073fe2d9fb0af16 in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=f171ed2 ]

[SYNCOPE-1292] Implementation provided


> Use Remote Key during Pull to match internal entities
> -
>
> Key: SYNCOPE-1292
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1292
> Project: Syncope
>  Issue Type: Improvement
>  Components: core
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.0.9, 2.1.0
>
>
> Following SYNCOPE-1182, extend the same approach to internal entities 
> matching during Pull, e.g. do not use {{__UID__}} but rather the value for 
> the attribute flagged as {{Remote Key}} in the Mapping.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SYNCOPE-1292) Use Remote Key during Pull to match internal entities

[JIRA]

Francesco Chicchiriccò created SYNCOPE-1292:
---

 Summary: Use Remote Key during Pull to match internal entities
 Key: SYNCOPE-1292
 URL: https://issues.apache.org/jira/browse/SYNCOPE-1292
 Project: Syncope
  Issue Type: Improvement
  Components: core
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
 Fix For: 2.0.9, 2.1.0


Following SYNCOPE-1182, extend the same approach to internal entities matching 
during Pull, e.g. do not use {{__UID__}} but rather the value for the attribute 
flagged as {{Remote Key}} in the Mapping.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: SYNCOPE-1270 : OpenID Connect client feature

[Isuranga Perera]

Hi Francesco,

Can you suggest a feature I can work on. I've previously worked in OpenID
Connect, SAML, SCIM and XACML projects. So appreciate if you can suggest a
feature/issue that I can work on.

Best Regards
Isuranga Perera

On Tue, Apr 3, 2018 at 4:31 PM, Dima Ayash  wrote:

> Dear,
>
> Thank you for your interest.
> The work has been done until now regarding this feature is:
> •The authorization code flow is the flow that is used for and "Google" as
> an example for the OpenID Provider.
> •To configure the OpenID Provider metadata to apply this flow, there are
> two ways depends on what the OpenID Provider supports, in case of
> supporting the Discovery  Document, requesting this document and process
> the response and stored the required values otherwise the user needs to
> insert these values.
> •The work used CXF OIDC dependency, and took benefits from the structure
> of SAML2.0 feature.
> •The work is still under progress, the core and the logic of the flow is
> done and tested, the user can have a session by logging successfully to his
> account in "Google" and by having a user in Apache Syncope.
>
> I would really appreciate questions for more details and also more
> suggestions to enhance this work.
>
> Thank you in advance and best regards,
> Dima Ayash.
>
>
> - Original Message -
> From: "Dima Ayash" 
> To: dev@syncope.apache.org
> Sent: Tuesday, April 3, 2018 12:56:02 PM
> Subject: Re: SYNCOPE-1270 : OpenID Connect client feature
>
> Dear,
>
> Thank you for your interest.
> The work has been done until now regarding this feature is:
> The authorization code flow is the flow that is used for and "Google" as
> an example for the OpenID Provider.
> To configure the OpenID Provider metadata to apply this flow, there are
> two ways depends on what the OpenID Provider supports, in case of
> supporting the Discovery  Document, requesting this document and process
> the response and stored the required values otherwise the user needs to
> insert this value.
> The work used CXF OIDC dependency, and took benefits from the structure of
> SAML2.0 feature.
> The work is still under progress, the core and the logic of the flow is
> done and tested, the user can have a session by logging successfully to his
> account in Google and by having a user in Apache Syncope.
>
>
> - Original Message -
> From: "Francesco Chicchiriccò" 
> To: dev@syncope.apache.org
> Sent: Tuesday, April 3, 2018 8:54:00 AM
> Subject: Re: SYNCOPE-1270 : OpenID Connect client feature
>
> On 03/04/2018 06:39, Isuranga Perera wrote:
> > Hi All,
> >
> > I would like to contribute $subject. I have contributed to WSO2 Identity
> > server and have worked with OpenID Connect and its profiles. Appreciate
> if
> > someone can provide me guidance throughout this feature.
> >
> > Best Regards
> > Isuranga Perera
>
> Dear Isuranga,
> thanks for your interest in Apache Syncope.
>
> As far as we know, there is already someone at work on the topic: see
>
> https://lists.apache.org/thread.html/d36e9354a4a638c7afc76a3e6d69aa
> f24d7c4e2c6a377e2ccfefcabe@%3Cdev.syncope.apache.org%3E
>
> Maybe you can pick one of the other feature requests from JIRA, or
> propose a new one.
>
> @Dima: could it be possible to provide a status update about your work
> there?
>
> 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] [Resolved] (SYNCOPE-1254) Cannot create new connector instances from Admin Console

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò resolved SYNCOPE-1254.
-
Resolution: Fixed

> Cannot create new connector instances from Admin Console
> 
>
> Key: SYNCOPE-1254
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1254
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.1.0
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.1.0
>
>
> In the modal window for Connector Instance creation, no Realms are shown for 
> administration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SYNCOPE-1254) Cannot create new connector instances from Admin Console

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425116#comment-16425116
 ] 

ASF subversion and git services commented on SYNCOPE-1254:
--

Commit 8ef021e23f67027dda842559029fd65788beb865 in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=8ef021e ]

[SYNCOPE-1254] Fighting (and losing) with Java 8 lambda


> Cannot create new connector instances from Admin Console
> 
>
> Key: SYNCOPE-1254
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1254
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.1.0
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.1.0
>
>
> In the modal window for Connector Instance creation, no Realms are shown for 
> administration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)