On 19/02/2013 14:13, Emmanuel Lécharny wrote:
Don't use uniqueMemeber. Never. Nine. Niet. Nix.
http://rfc-ref.org/RFC-TEXTS/4519/chapter2.html#d4e443387
This is far from what you expect it to be, and you'll get hard time with some
Windows identifier having a # in their DN.
Hi Emmanuel,
what'
[
https://issues.apache.org/jira/browse/SYNCOPE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-319.
Resolution: Fixed
http://svn.apache.org/r1448090
> Provid
[
https://issues.apache.org/jira/browse/SYNCOPE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-209.
Resolution: Fixed
Resolving as part of SYNCOPE-319
> DB T
[
https://issues.apache.org/jira/browse/SYNCOPE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582116#comment-13582116
]
Francesco Chicchiriccò commented on SYNCOPE-319:
REST API upgrade wiki pa
[
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò reassigned SYNCOPE-293:
--
Assignee: Francesco Chicchiriccò (was: Massimiliano Perrone)
> Sh
Colm O hEigeartaigh created SYNCOPE-320:
---
Summary: Support synchronizing role memberships from LDAP
groupOfNames
Key: SYNCOPE-320
URL: https://issues.apache.org/jira/browse/SYNCOPE-320
Project:
Patch submitted for review here:
https://issues.apache.org/jira/browse/SYNCOPE-320
Colm.
On Mon, Feb 18, 2013 at 5:14 PM, Francesco Chicchiriccò wrote:
> On 18/02/2013 16:08, Colm O hEigeartaigh wrote:
>
>> [...]
>>
>>
>> LDAPMembershipPropagationActio**ns has "ldapGroups" as the group member
[
https://issues.apache.org/jira/browse/SYNCOPE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated SYNCOPE-320:
Attachment: syncope-320.patch
A patch for this issue.
Colm.
> S
> think that we can move Syncope 1.1.0 to ConnId 1.3.3-SNAPSHOT, thus avoid
> branching.
>
Any objections to me moving the Syncope trunk pom to use 1.3.3-SNAPSHOT,
and the SNAPSHOT versions of the Connector bundles?
Colm.
On Tue, Feb 19, 2013 at 2:19 PM, Colm O hEigeartaigh wrote:
>
> Given the
On 20/02/2013 13:28, Colm O hEigeartaigh wrote:
I think that we can move Syncope 1.1.0 to ConnId 1.3.3-SNAPSHOT, thus avoid
branching.
Any objections to me moving the Syncope trunk pom to use 1.3.3-SNAPSHOT,
and the SNAPSHOT versions of the Connector bundles?
Not at all, go ahead.
Regards.
[
https://issues.apache.org/jira/browse/SYNCOPE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-320:
---
Component/s: core
Affects Version/s: 1.1.0
> Support synchroni
[
https://issues.apache.org/jira/browse/SYNCOPE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582143#comment-13582143
]
Francesco Chicchiriccò commented on SYNCOPE-320:
Patch looks good to me:
Il giorno 20/feb/2013, alle ore 13.28, Colm O hEigeartaigh ha scritto:
>> think that we can move Syncope 1.1.0 to ConnId 1.3.3-SNAPSHOT, thus avoid
>> branching.
>>
>
> Any objections to me moving the Syncope trunk pom to use 1.3.3-SNAPSHOT,
> and the SNAPSHOT versions of the Connector bundles?
The Apache Jenkins build system has built Syncope-trunk (build #102)
Status: Failure
Check console output at https://builds.apache.org/job/Syncope-trunk/102/ to
view the results.
[
https://issues.apache.org/jira/browse/SYNCOPE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582160#comment-13582160
]
Hudson commented on SYNCOPE-319:
Integrated in Syncope-trunk #102 (See
[https://builds.a
[
https://issues.apache.org/jira/browse/SYNCOPE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582161#comment-13582161
]
Hudson commented on SYNCOPE-209:
Integrated in Syncope-trunk #102 (See
[https://builds.a
Le 2/20/13 11:26 AM, Francesco Chicchiriccò a écrit :
> On 19/02/2013 14:13, Emmanuel Lécharny wrote:
>> Don't use uniqueMemeber. Never. Nine. Niet. Nix.
>>
>> http://rfc-ref.org/RFC-TEXTS/4519/chapter2.html#d4e443387
>>
>> This is far from what you expect it to be, and you'll get hard time
>> with
Hi Syncoper,
Here are some more best practices for RESTful APIs.
Use PUT if you want to persist an entity as it is. Use POST from any kind of
processes.
Hence I would recommend to change:
PUT /connectors/reload
To
POST /connectors/reload
Best regards.
Jan
From: conflue...@apache.org [mailto
On 20/02/2013 15:13, Jan Bernhardt wrote:
Hi Syncoper,
Here are some more best practices for RESTful APIs.
Use PUT if you want to persist an entity as it is. Use POST from any kind of
processes.
Hence I would recommend to change:
PUT /connectors/reload
To
POST /connectors/reload
Hi Jan, t
[
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-293.
Resolution: Fixed
http://svn.apache.org/r1448184
> Show i
[
https://issues.apache.org/jira/browse/SYNCOPE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved SYNCOPE-320.
-
Resolution: Fixed
> Support synchronizing role memberships from LDAP groupOf
[
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated SYNCOPE-293:
Attachment: Screenshot from 2013-02-20.png
Sorry to be a PITA, but I'm seeing the
[
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582243#comment-13582243
]
Francesco Chicchiriccò commented on SYNCOPE-293:
You need to either re-ge
Hi all,
>From the wiki:
https://cwiki.apache.org/confluence/display/SYNCOPE/REST+API+upgrade#RESTAPIupgrade-UserService
GET /user/verifyPassword/{username}?password={password} GET
/users?username={username}&pwd={password} Returns user if username and
password match with an existing account.
Th
[
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582261#comment-13582261
]
Colm O hEigeartaigh commented on SYNCOPE-293:
-
Yup that works, sorry for the
Hi Colm,
The description is wrong, this method returns a boolean.
Best regards.
Jan
> -Original Message-
> From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
> Sent: Mittwoch, 20. Februar 2013 16:48
> To: dev@syncope.apache.org
> Subject: API query
>
> Hi all,
>
> From the wiki:
>
Thanks Jan, I have updated it. The "old" API method returns "null" if the
User does not exist, whereas the new API does not seem to return anything.
Would it not be better in both cases to return "false" explicitly? Or are
there backwards compatilbity concerns about changing this?
Colm.
On Wed, F
A second thought is that a API to return the User matching the given
username + password would be quite nice, unless there is another way of
doing this that I am missing. WDYT?
Colm.
On Wed, Feb 20, 2013 at 4:04 PM, Colm O hEigeartaigh wrote:
>
> Thanks Jan, I have updated it. The "old" API meth
I wonder if
"GET /users?username={username}&pwd={password}"
is safe enough, as these URIs might get cached somewhere given it is GET
(though not sure if the caching of URIs can happen with HTTPS).
Might make sense considering treating this as an action request, with
the credentials being POS
On 20/02/2013 15:15, Francesco Chicchiriccò wrote:
On 20/02/2013 15:13, Jan Bernhardt wrote:
Hi Syncoper,
Here are some more best practices for RESTful APIs.
Use PUT if you want to persist an entity as it is. Use POST from any
kind of processes.
Hence I would recommend to change:
PUT /conne
[
https://issues.apache.org/jira/browse/SYNCOPE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582437#comment-13582437
]
Hudson commented on SYNCOPE-319:
Integrated in Syncope-trunk #103 (See
[https://builds.a
[
https://issues.apache.org/jira/browse/SYNCOPE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582440#comment-13582440
]
Hudson commented on SYNCOPE-320:
Integrated in Syncope-trunk #103 (See
[https://builds.a
[
https://issues.apache.org/jira/browse/SYNCOPE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582439#comment-13582439
]
Hudson commented on SYNCOPE-310:
Integrated in Syncope-trunk #103 (See
[https://builds.a
[
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582438#comment-13582438
]
Hudson commented on SYNCOPE-293:
Integrated in Syncope-trunk #103 (See
[https://builds.a
[
https://issues.apache.org/jira/browse/SYNCOPE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582441#comment-13582441
]
Hudson commented on SYNCOPE-209:
Integrated in Syncope-trunk #103 (See
[https://builds.a
The Apache Jenkins build system has built Syncope-trunk (build #103)
Status: Still Failing
Check console output at https://builds.apache.org/job/Syncope-trunk/103/ to
view the results.
36 matches
Mail list logo