Re: Understanding connector agent in remote system
Hi, a ConnId Connector Server [1] can be essentially seen as a remote container for connector bundles. Normally, Syncope is configured to look up for connector bundles from a local directory, but there are more options [2], including referencing connector servers. Once a (Java or .Net) connector server is set up and running, Syncope will be able to use the connector bundles deployed there as if they were instead deployed in a local directory. As you can imagine, this is especially useful when, for example, you are running Syncope on Linux but need to provision by using PowerShell scripts, which require to be run on Windows. In this case, all you need is to 1. deploy a Java connector server on Windows 2. deploy the ConnId CMD bundle [3] onto such connector server 3. write the PowerShell scripts 4. configure Syncope (as explained in [2]) for using such connector server 5. use the Admin Console to configure the CMD bundle as if it was deployed locally The communication between Syncope and ConnId connector servers is based on a TCP protocol defined by ConnId, which can also use SSL (as explained in [2]). HTH Regards. On 22/02/2017 14:22, Tech wrote: Dear experts, we checked from the documentation that the conn bundles could be also deployed on the target system instead of that in Syncope. We want to understand with you if it would be possible to configure a similar scenario and to validate if our understanding is correct: * Syncope is deployed on Server1 and the target system on the Server2. * Syncope calls the remote connector deployed on the Server2 (using REST?) * The remote connector deployed on Server2 extracts the data (SELECT FIRSTNAME, LASTNAME FROM USER;) * The remote connector caches the result of the query * Syncope extract the information from the remote connector and take them to Server1. Is that correct? Thanks -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Enduser interface - Enum values
Thanks Andrea, looking forward for version 2.0.3 On 02/23/2017 10:27 AM, Andrea Patricelli wrote: t configuration, there is a bug in the Enduser, it does not support labels longer than 1 character. I've just open [1]. Fix will be available since 2.0.3 release (and in 2.0.3-SNAPSHOT). Best regards,
Re: Error in synchronize data from LDAP to syncope
Hi Rajkumar,
if you are still using Active Directory as resource, like Massimiliano
Perrone correctly pointed out yesterday, please use the Active Directory
connector instead of LDAP connector!
Maybe [1] could help you with connectors installation.
Best regards,
Andrea
[1]
https://syncope.apache.org/docs/reference-guide.html#install-connector-bundles
Il 23/02/2017 12:26, rajkumar ha scritto:
Hi All,
Below are the details i have provided in syncope 2.0.2 console and i tried
to synchronize data from LDAP to syncope :
Details:
*Connector :*
---
Location : file:/opt/Cognizant/syncope/bundles/
Bundle : net.tirasa.connid.bundles.ldap.schema.LdapSchemaMapping
Version : 1.5.1
Host : <>
TCP Port : 389
Principle : <>
Password : <>
Base Context : OU=MUL,DC=loc,DC=trumobi,DC=de
Account User Name attribute : uid, cn
LDAP Filter for Retrieving Accounts : cn=*
Group Name Attributes = cn
Group Member Attribute : member
Base Contexts to Synchronize : OU=MUL,DC=loc,DC=trumobi,DC=de
capabilities : search, create, update, sync
*Resource :*
--
Propagation Action : LDAPMembershipSyncActions
capabilities : search, create, update, sync
Provisions rules:
object type : user
Object Class : account
classes : BaseGroup
*Mapping:*
username cn true remote_key
surname sn true ---
Object link : 'cn=' + username + ',DC=loc,DC=trumobi,DC=de'
I am getting below error in connid.log
*[2017-02-23T11:19:46.403]
net.tirasa.connid.bundles.ldap.schema.LdapSchemaMapping
Attribute __ENABLE__ of object class __ACCOUNT__ is not mapped to an LDAP
attribute Method: getLdapAttribute*
*[2017-02-23T11:19:46.403]
org.identityconnectors.framework.common.objects.ResultsHandler
Enter: {Uid=Attribute: {Name=__UID__, Value=[Bernd_S_epS]},
ObjectClass=ObjectClass: __ACCOUNT__, Attributes=[Attribute: {Name=__NAME__,
Value=[CN=Bernd_S_epS,OU=G_GI_GEO_epS,OU=MUL,DC=loc,DC=trumobi,DC=de]},
Attribute: {Name=cn, Value=[Bernd_S_epS]}, Attribute: {Name=sn, Value=[]},
Attribute: {Name=__UID__, Value=[Bernd_S_epS]}, Attribute: {Name=__ENABLE__,
Value=[]}], 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 with this to fix the issue. Let me know what i am missing
here.
--
View this message in context:
http://syncope-user.1051894.n5.nabble.com/Error-in-synchronize-data-from-LDAP-to-syncope-tp5709016.html
Sent from the syncope-user mailing list archive at Nabble.com.
--
Andrea Patricelli
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope
Re: Enduser interface - Enum values
Hi, No, you are using a right configuration, there is a bug in the Enduser, it does not support labels longer than 1 character. I've just open [1]. Fix will be available since 2.0.3 release (and in 2.0.3-SNAPSHOT). Best regards, Andrea [1] https://issues.apache.org/jira/browse/SYNCOPE-1024 Il 23/02/2017 10:05, Tech ha scritto: Dear experts, we created a custom Enum type "p_language" The mappings should be * 1: English * 2: German translated in this way Type: Enum values * 1 * 2 Labels * English * German Basic validator When we enter in the user interface we see in the dropdown * E * N * G while we are expecting * English * German Could you please doublecheck or confirm us if we are using a wrong configuration? Thanks -- Andrea Patricelli Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope
Enduser interface - Enum values
Dear experts, we created a custom Enum type "p_language" The mappings should be * 1: English * 2: German translated in this way Type: Enum values * 1 * 2 Labels * English * German Basic validator When we enter in the user interface we see in the dropdown * E * N * G while we are expecting * English * German Could you please doublecheck or confirm us if we are using a wrong configuration? Thanks
