[jira] [Commented] (SYNCOPE-1174) NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema is present

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh commented on SYNCOPE-1174:
--

It was just an issue I ran into while upgrading from 2.0.2 to 2.0.4. NPE checks 
for all of the schemas is probably overkill. I'm happy to revert it if you 
object?

> NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema is 
> present
> ---
>
> Key: SYNCOPE-1174
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1174
> Project: Syncope
>  Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
>Priority: Trivial
> Fix For: 2.0.5, 2.1.0
>
>
> There is a NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' 
> schema is present in the relevant Content.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1174) NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema is present

[JIRA]

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

Francesco Chicchiriccò commented on SYNCOPE-1174:
-

The fix is to create the conf schema, as the upgrade guide says.
It's plenty of conf schemas in the code, which are either loaded from 
Content.xml or asked to be created during upgrade: shall we introduce NPE 
checks for all of them?

> NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema is 
> present
> ---
>
> Key: SYNCOPE-1174
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1174
> Project: Syncope
>  Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
>Priority: Trivial
> Fix For: 2.0.5, 2.1.0
>
>
> There is a NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' 
> schema is present in the relevant Content.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (SYNCOPE-1174) NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema is present

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh resolved SYNCOPE-1174.
--
Resolution: Fixed

> NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema is 
> present
> ---
>
> Key: SYNCOPE-1174
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1174
> Project: Syncope
>  Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
>Priority: Trivial
> Fix For: 2.0.5, 2.1.0
>
>
> There is a NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' 
> schema is present in the relevant Content.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1174) NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema is present

[ASF subversion and git services (JIRA)]

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

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

Commit 6634daaeebbe95fea9e1c104bc64d7b2e0d45e4b in syncope's branch 
refs/heads/2_0_X from [~coheigea]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=6634daa ]

SYNCOPE-1174 - NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' 
schema is present


> NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema is 
> present
> ---
>
> Key: SYNCOPE-1174
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1174
> Project: Syncope
>  Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
>Priority: Trivial
> Fix For: 2.0.5, 2.1.0
>
>
> There is a NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' 
> schema is present in the relevant Content.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SYNCOPE-1174) NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema is present

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-1174:


 Summary: NPE in AccessTokenDataBinderImpl if no 
'jwt.lifetime.minutes' schema is present
 Key: SYNCOPE-1174
 URL: https://issues.apache.org/jira/browse/SYNCOPE-1174
 Project: Syncope
  Issue Type: Bug
Affects Versions: 2.0.4
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
Priority: Trivial
 Fix For: 2.0.5, 2.1.0


There is a NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema 
is present in the relevant Content.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1174) NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema is present

[ASF subversion and git services (JIRA)]

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

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

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

SYNCOPE-1174 - NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' 
schema is present


> NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' schema is 
> present
> ---
>
> Key: SYNCOPE-1174
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1174
> Project: Syncope
>  Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
>Priority: Trivial
> Fix For: 2.0.5, 2.1.0
>
>
> There is a NPE in AccessTokenDataBinderImpl if no 'jwt.lifetime.minutes' 
> schema is present in the relevant Content.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SYNCOPE-1166) No propagation task is created for resources where the password is not propagated

[Marco Di Sabatino Di Diodoro (JIRA)]

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

Marco Di Sabatino Di Diodoro updated SYNCOPE-1166:
--
Attachment: SYNCOPE-1166-test.patch

I implemented the test for this issue.

> No propagation task is created for resources where the password is not 
> propagated
> -
>
> Key: SYNCOPE-1166
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1166
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 2.0.4
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
> Fix For: 2.0.5, 2.1.0
>
> Attachments: SYNCOPE-1166-test.patch
>
>
> During a propagation, if one of the resources assigned to the user doesn't 
> need to propagate the password but other fields, Syncope doesn't generate the 
> task for that resource.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1167) Preliminary AnyType selection when adding new provision rule

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SYNCOPE-1167:
-

GitHub user mat-ale opened a pull request:

https://github.com/apache/syncope/pull/57

[SYNCOPE-1167] Preliminary AnyType selection when adding new provision rule

Hi,

this fixes 
[[SYNCOPE-1167]](https://issues.apache.org/jira/browse/SYNCOPE-1167).

Regards,
Matteo

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mat-ale/syncope SYNCOPE-1160

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/syncope/pull/57.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #57


commit c64706bf8e85c8e346f23a58c8789b8163b4d897
Author: Matteo Alessandroni 
Date:   2017-07-25T14:27:43Z

[SYNCOPE-1167] Preliminary AnyType selection when adding new provision rule




> Preliminary AnyType selection when adding new provision rule
> 
>
> Key: SYNCOPE-1167
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1167
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
> Fix For: 2.0.5, 2.1.0
>
>
> Currently, the selection of an AnyType is part of the wizard for provision 
> rule, in the first step of create.
> Later, when editing a provision rule, the icon makes jumping into the second 
> step of such wizard, and pressing the {{Prev}} button leads to 
> inconsistencies, as reported by SYNCOPE-1160.
> If the AnyType selection is moved away from the wizard - and placed into a 
> separate {{TogglePanel}} to be displayed only during cerate - such quirks 
> should be solved at once.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (SYNCOPE-1173) Replace List dynGroups with List dynMemberships

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh resolved SYNCOPE-1173.
--
Resolution: Fixed

> Replace List dynGroups with List dynMemberships
> -
>
> Key: SYNCOPE-1173
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1173
> Project: Syncope
>  Issue Type: Improvement
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
> Fix For: 2.0.5, 2.1.0
>
>
> This task is to replace List dynGroups with List 
> dynMemberships in UserTO and AnyObjectTO. This will allow us to retrieve the 
> dynamic group names associated with a given user or Any Object when doing a 
> GET, as opposed to the current situation where we only see the keys of the 
> group.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)