[
https://issues.apache.org/jira/browse/SYNCOPE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-193.
--------------------------------------------
Resolution: Not A Problem
Assignee: Francesco Chicchiriccò
The sample StatusManager provided
(org.connid.bundles.ldap.commons.AttributeStatusManagement - see source [1])
uses the inetOrgPerson's 'description' attribute - with values 'Active' /
'Inactive' - in order to determine user status on LDAP: when description has a
different value, an unknown status is returned and a question mark appears on
the admin console.
When you create an user from Syncope and then propagate to LDAP, the
'description' value is pushed in the right format.
When you synchronize from LDAP, it only depends on the 'description' value you
have on your LDAP entries.
I'd like to stress that AttributeStatusManagement is provided for sample and
test purposes and that, since LDAP does not provide a standard mechanism for
checking user status, this is likely in the need to be adjusted on each
specific Syncope deployment.
[1]
http://connid.googlecode.com/svn/bundles/ldap/trunk/src/main/java/org/connid/bundles/ldap/commons/AttributeStatusManagement.java
> LDAP test connector status management does not work with synchronization
> ------------------------------------------------------------------------
>
> Key: SYNCOPE-193
> URL: https://issues.apache.org/jira/browse/SYNCOPE-193
> Project: Syncope
> Issue Type: Bug
> Affects Versions: 1.0.1-incubating
> Reporter: Colm O hEigeartaigh
> Assignee: Francesco Chicchiriccò
> Priority: Minor
> Fix For: 1.0.2-incubating, 1.1.0-incubating
>
>
> SYNCOPE-184 added a default Status Management class for the LDAP Connector.
> However it only appears to work with propagation, i.e. create a New user and
> propagate to the resource and the green icon appears. But when users are
> added via synchronization, the old question mark icon appears instead.
--
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
