Hi Massi,

Really sorry, I am using LDAP connector to connect LDAP and I have given
all attributes value. Still getting the same issue. Kindly help me to fix
the same.

Thanks,
Rajkumar K
On Feb 23, 2017 12:30 AM, "Raj Kumar" <rajkani8...@gmail.com> wrote:

> Hi,
>
> I didn't find AD connector in my drop down value. And found only the LDAP
> connector, which I thought for both AD and LDAP having same connector.
>
> Thanks,
> Rajkumar k
> On Feb 23, 2017 12:17 AM, "Massimiliano Perrone" <
> massimiliano.perr...@tirasa.net> wrote:
>
> Hi,
> only curiosity, but why you are using the LDAP connector when AD connector
> exists and it is the right one?
>
> Massi
>
> --
> Massimiliano Perrone
> Tel +39 393 9121310
> Tirasa S.r.l.
> http://www.tirasa.net
>
> "L'apprendere molte cose non insegna l'intelligenza"
> (Eraclito)
> mercoledì, 22 febbraio 2017, 07:08PM +01:00 da Raj Kumar
> rajkani8...@gmail.com:
>
>
> And if you see in below details.
>
> {Name=__UID__, Value=[Bernd_S_epS]}, Attribute: {Name=__ENABLE__,
> Value=[]}, Attribute: {Name=name, Value=[Bernd_S_epS]}], Name=Attribute:
> {Name=__NAME__,
> Value=[CN=Bernd_S_epS,OU=G_GI_GEO_epS,OU=MUL,DC=loc,DC=trumobi,DC=de]}}
> Method: handle*
>
> I have given name and uid when I did mapping,  but not sure from where the
> value __ENABLE__ is coming from. Kindly If you have any idea, could you
> share?
>
> In my mapping section I am adding username, password and surname. Other
> than that I didn't mapped any value but not sure "surname" is in AD. That
> will cause problem if that surname attribute not in AD right?
>
> Thanks,
> Rajkumar k
>
> Thanks,
> Rajkumar k
> On Feb 22, 2017 11:30 PM, "Raj Kumar" <rajkani8...@gmail.com> wrote:
>
> I am using LDAP connector. For that I need to do any additional
> configuration?.
>
> But I am synchronizing data from AD to syncope. Is there different
> connector for AD and LDAP?
>
> Thanks,
>
> Rajkumar K
> On Feb 22, 2017 11:17 PM, "Andrea Patricelli" <
> andrea.patrice...@tirasa.net> wrote:
>
> Hi RajKumar,
>
> Are you using AD connector or the LDAP connector?
> In the AD connector status is managed internally, you shouldn't get such
> error.
>
> Best regards,
> Andrea
>
> Inviato da BlueMail <http://www.bluemail.me/r?b=8872>
> Il giorno 22 feb 2017, alle ore 16:20, rajkumar <rajkani8...@gmail.com>
> ha scritto:
>
> Hi,
>
> I have set up syncope 2.0.2 in my centos server and i have created connector
> for sync data from AD to Syncope. I have checked the connection and there
> are no issues.
>
> But when i try to run the pull task, it is giving success status but in
> connid.log i am getting below error.
>
> *[2017-02-22T15:09:51.998]
> net.tirasa.connid.bundles.ldap.schema.LdapSchemaMapping
> Attribute __ENABLE__ of object class __ACCOUNT__ is not mapped to an LDAP
> attribute Method: getLdapAttribute
> [2017-02-22T15:09:51.998]
> org.identityconnectors.framework.common.objects.ResultsHandler
> Enter: {Uid=Attribute: {Name=__UID__, Value=[Bernd_S_epS]},
> ObjectClass=ObjectClass: __ACCOUNT__, Attributes=[Attribute:
> {Name=__PASSWORD__,
> Value=[org.identityconnectors.common.security.GuardedString@204e249b]},
> Attribute: {Name=__NAME__,
> Value=[CN=Bernd_S_epS,OU=G_GI_GEO_epS,OU=MUL,DC=loc,DC=trumobi,DC=de]},
> Attribute: {Name=__UID__, Value=[Bernd_S_epS]}, Attribute: {Name=__ENABLE__,
> Value=[]}, Attribute: {Name=name, Value=[Bernd_S_epS]}], Name=Attribute:
> {Name=__NAME__,
> Value=[CN=Bernd_S_epS,OU=G_GI_GEO_epS,OU=MUL,DC=loc,DC=trumobi,DC=de]}}
> Method: handle*
>
> Kindly help me in this to fix the issue.
>
> Thanks in advance
>
> Rajkumar K
>
> --
> View this message in context: 
> http://syncope-user.1051894.n5.nabble.com/Get-error-while-try-to-synchronize-AD-data-to-syncpe-tp5709003.html
> Sent from the syncope-user mailing list archive at Nabble.com.
>
>

Reply via email to