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

Francesco Chicchiriccò commented on SYNCOPE-265:
------------------------------------------------

About items found so far:

1. ldap connector: I will take care of updating the configuration in order to 
make the "check connection" work

2. ws-target-resource-3's purpose is to show the timeout handling feature 
introduced by SYNCOPE-279, so it has to stay this way: I will rename it as 
'ws-target-resource-timeout' to make its purpose more clear

3. ws-target-resource-2 propagation fails for role 8: even though the error 
message can be made more meaningful ([1] was opened for this), the SOAP 
connector does not support GROUP objectclass, hence propagation will keep 
failing; a possible solution is to either remove this resource from role 8 or 
to change it to resource-ldap (the LDAP connector is the only one publicly 
available supporting GROUP objectclass, even though this is on the roadmap for 
the AD connector [2]).

[1] https://connid.atlassian.net/browse/SOAP-5
[2] https://connid.atlassian.net/browse/AD-1
                
> Ensure that Syncope test data is consistent
> -------------------------------------------
>
>                 Key: SYNCOPE-265
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-265
>             Project: Syncope
>          Issue Type: Task
>            Reporter: Colm O hEigeartaigh
>            Assignee: Massimiliano Perrone
>            Priority: Minor
>             Fix For: 1.1.0
>
>
> This task is to ensure that the test data is consistent since it is used for 
> embedded mode [1] and in standalone distribution (as per SYNCOPE-206).
> For example, Users do not conform to the Schema: currently "user1" is missing 
> values for the required attributes "surname" and "userId". 
> [1] 
> https://cwiki.apache.org/confluence/display/SYNCOPE/Run+Syncope+in+embedded+mode

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to