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

Hudson commented on SYNCOPE-184:
--------------------------------

Integrated in Syncope-linux-branches #12 (See 
[https://builds.apache.org/job/Syncope-linux-branches/12/])
    [SYNCOPE-184] User status information now shown for LDAP resource + all 
ConnId bundles updated to latest versions (Revision 1378499)

     Result = SUCCESS
ilgrosso : 
Files : 
* 
/incubator/syncope/branches/1_0_X/archetype/src/main/resources/archetype-resources/console/pom.xml
* 
/incubator/syncope/branches/1_0_X/archetype/src/main/resources/archetype-resources/core/pom.xml
* /incubator/syncope/branches/1_0_X/build-tools/pom.xml
* /incubator/syncope/branches/1_0_X/console/pom.xml
* /incubator/syncope/branches/1_0_X/core/pom.xml
* 
/incubator/syncope/branches/1_0_X/core/src/test/java/org/apache/syncope/core/rest/ConnInstanceTestITCase.java
* 
/incubator/syncope/branches/1_0_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java
* /incubator/syncope/branches/1_0_X/core/src/test/resources/content.xml
* /incubator/syncope/branches/1_0_X/parent/pom.xml

                
> LDAP test connector should provide status information
> -----------------------------------------------------
>
>                 Key: SYNCOPE-184
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-184
>             Project: Syncope
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.0.0-incubating
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 1.0.1-incubating, 1.1.0-incubating
>
>
> No conf value is provided for LDAP connector's statusManagementClass
> Note: this is not a problem itself, and is also the reason why you can see 
> the 'undefined icon' on the console; anyway, it would be nice to provide a 
> complete configuration

--
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