Il giorno 08/gen/2013, alle ore 17.46, Colm O hEigeartaigh ha scritto:
> Hi Fabio,
>
>> If the new subscribed resource doesn't require password value, then a new
> password specification shouldn't be required.
>> WDYT?
>
> +1. Thanks for the explanation.
>
>> This sounds a little bit strange.
Hi Fabio,
> If the new subscribed resource doesn't require password value, then a new
password specification shouldn't be required.
> WDYT?
+1. Thanks for the explanation.
> This sounds a little bit strange.
> Let me understand ...
> 1. you synchronize a new user
> 2. you retrieve user details (
The Apache Jenkins build system has built Syncope-trunk (build #415)
Status: Fixed
Check console output at https://builds.apache.org/job/Syncope-trunk/415/ to
view the results.
[
https://issues.apache.org/jira/browse/SYNCOPE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546832#comment-13546832
]
Hudson commented on SYNCOPE-267:
Integrated in Syncope-trunk #415 (See
[https://builds.a
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546831#comment-13546831
]
Hudson commented on SYNCOPE-259:
Integrated in Syncope-trunk #415 (See
[https://builds.a
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546827#comment-13546827
]
Jan Bernhardt commented on SYNCOPE-259:
---
Done. Each REST-Service know has a Service
Ups. Sorry for that! I use 9081 for my TCP Monitor...
Best regards.
Jan
> -Original Message-
> From: fmarte...@apache.org [mailto:fmarte...@apache.org]
> Sent: Dienstag, 8. Januar 2013 12:48
> To: comm...@syncope.apache.org
> Subject: svn commit: r1430227 - in /syncope/trunk/core/src/tes
The Apache Jenkins build system has built Syncope-trunk (build #414)
Status: Unstable
Check console output at https://builds.apache.org/job/Syncope-trunk/414/ to
view the results.
[
https://issues.apache.org/jira/browse/SYNCOPE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546808#comment-13546808
]
Hudson commented on SYNCOPE-267:
Integrated in Syncope-trunk #414 (See
[https://builds.a
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546807#comment-13546807
]
Hudson commented on SYNCOPE-259:
Integrated in Syncope-trunk #414 (See
[https://builds.a
[
https://issues.apache.org/jira/browse/SYNCOPE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546802#comment-13546802
]
Hudson commented on SYNCOPE-267:
Integrated in Syncope-1_0_X #97 (See
[https://builds.ap
[
https://issues.apache.org/jira/browse/SYNCOPE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli resolved SYNCOPE-267.
Resolution: Fixed
> Possible NullPointerException into SchemaMappingUtil.getAccountIdV
[
https://issues.apache.org/jira/browse/SYNCOPE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli reassigned SYNCOPE-267:
--
Assignee: fabio martelli
> Possible NullPointerException into SchemaMappingUtil.ge
fabio martelli created SYNCOPE-267:
--
Summary: Possible NullPointerException into
SchemaMappingUtil.getAccountIdValue()
Key: SYNCOPE-267
URL: https://issues.apache.org/jira/browse/SYNCOPE-267
Project:
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546733#comment-13546733
]
Hudson commented on SYNCOPE-259:
Integrated in Syncope-trunk #413 (See
[https://builds.a
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546702#comment-13546702
]
Jan Bernhardt commented on SYNCOPE-259:
---
Workflow- and NotifificationService are al
[
https://issues.apache.org/jira/browse/SYNCOPE-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli reassigned SYNCOPE-266:
--
Assignee: fabio martelli
> Password should be provided again at resource subscript
Il giorno 08/gen/2013, alle ore 08.49, Jan Bernhardt ha scritto:
>>> Ok thanks. However I can't seem to subscribe the User to a new
>>> Resource even by specifying the password - I guess it is complaining
>>> that the new password is the same as the old one. So there is no way
>>> to propagate an
fabio martelli created SYNCOPE-266:
--
Summary: Password should be provided again at resource
subscription time if a "Password" schema mapping for that resource exists
Key: SYNCOPE-266
URL: https://issues.apache.or
19 matches
Mail list logo