You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@syncope.apache.org by Martin van Es <mr...@gmail.com> on 2012/10/12 22:24:49 UTC
csvdir connector
Hi,
My name is Martin and I'm making my first steps into Syncope. In line
of my expertise as an Identity Manager (NetIQ) consultant, my first
goal is just to experiment and see what it can do and so far I was
able to setup syncope + ldap. Now however I'd like to sync the
accounts to CSV file just for simple reason of inspection of the
synchronisation result and fun.
I configured the csvdir connector to contain several columns and
assigned one of them to the keyColumnNames (uname). In the resources
tab I carefuly configured the Username to be mapped as AccountId
(which is the equivalent of "uname becomes username" as far as I
understand the LDAP example. The rest of the colums are assigned
arbitrary values. I am able to succesfully sync the user to csv but,
the username never gets synced to the file. The contents perfectly
reflect the user details, except for the username (which is key) and
is set to "null". And thus I can't retrieve status information of the
user and after reconciliation I get a new user "null" added to the
repository.
Questions:
Is the csvdir connector broken, or do I miss something?
What would be the correct setting for "Account link" in the csvdir
connector? I've set it to anything ranging from empty to 'uname=' +
username, but nothing happens to the Account Link column of the
account after synchronisation (it always shows an empty string, where
the LDAP resource shows uid=foobar,ou=people,dc=foo,dc=nl).
Best regards,
Martin
--
If 'but' was any useful, it would be a logic operator
Re: csvdir connector
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 19/10/2012 10:06, Martin van Es wrote:
> Hi Francesco,
>
> On Thu, Oct 18, 2012 at 3:23 PM, Francesco Chicchiriccò<il...@apache.org> wrote:
>> Martin,
>> a couple of thoughts:
>>
>> 1. One way to accomplish your task (i.e. upgrade the connector bundle version in an existing connector instance) without being forced to re-define all the components named above would have been to export the
>> configuration as XML, make the necessary correction and then re-import the modified content.xml.
> Its good to know that path exists, I was nearly diving into the database to see where the connector values were stored ;)
>
>> I agree that this is not "production-ready" but it mostly fits in a dev scenario.
> If it works realiable, I don't see why that wouldn't be production ready. I don't need fancy buttons, I asked for a way to not have to reassociate thousands of users to a new resource. This would fit the bill I guess?
Yes, but I personally don't see this feature as completely mature yet:
consider that you cannot currently select what to export or import: it's
always the *whole* db.
This means that it's fine to make some changes "under the hood" on a dev
scenario where there are possibly few users (which are by far the
highest data volume in Syncope), but in production...
>> 2. ...
>> Instead, we could allow to change the connector instance of an existing resource
> That would be the next best alternative and get my vote immediately!
> It would also allow for quick connector debugging in dev environment.
It took some time, but I've finally been able to open an issue for this:
https://issues.apache.org/jira/browse/SYNCOPE-229
> Even better: It would allow for switching between test/prod resources without having to reassociate the synchronisation tasks... don't know if that's smart, but it'd be nice to have the possibility.
Hum, I don't see this as a best practice: I'd rather define two separate
synchronization tasks associated respectively with test / prod resources
so that I could better track what's happening: the trace level is
customizable, for example...
Regards.
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Re: csvdir connector
Posted by Martin van Es <mr...@gmail.com>.
Hi Francesco,
On Thu, Oct 18, 2012 at 3:23 PM, Francesco Chicchiriccò
<il...@apache.org> wrote:
> Martin,
> a couple of thoughts:
>
> 1. One way to accomplish your task (i.e. upgrade the connector bundle
> version in an existing connector instance) without being forced to
> re-define all the components named above would have been to export the
> configuration as XML, make the necessary correction and then re-import
> the modified content.xml.
Its good to know that path exists, I was nearly diving into the
database to see where the connector values were stored ;)
> I agree that this is not "production-ready" but it mostly fits in a dev
> scenario.
If it works realiable, I don't see why that wouldn't be production
ready. I don't need fancy buttons, I asked for a way to not have to
reassociate thousands of users to a new resource. This would fit the
bill I guess?
> 2. ...
> Instead, we could allow to change the connector instance of an existing
> resource
That would be the next best alternative and get my vote immediately!
It would also allow for quick connector debugging in dev environment.
Even better: It would allow for switching between test/prod resources
without having to reassociate the synchronisation tasks... don't know
if that's smart, but it'd be nice to have the possibility.
Martin
--
If 'but' was any useful, it would be a logic operator
Re: csvdir connector
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 18/10/2012 08:47, Martin van Es wrote:
> Hi Francesco,
>
> On Wed, Oct 17, 2012 at 6:04 PM, Francesco Chicchiriccò<il...@apache.org> wrote:
>> FYI, CSVDir connector bundle 0.5 (including this fix) was released yesterday: I've updated the SNAPSHOT versions to include it.
> Thx for the quick fix!
>
> Dropped the csvdir 0.5 jar in my bundles dir and it works. One remark however: It's a PITA to deploy this new connector because I can not reassign a new bundle to an existing connector, nor was I able to assign a different connector to an existing resource. I even had to reconstruct my synchronisation task!
> I realise this scenario is not likely to happen in production, but I don't want to think about the complications of un- and re-assigning 10.000+ resources to my population just because a critical bug or
> feature xyz was fixed in some back-end driver?! Maybe we could at least think of a way to allow reassigning connector bundles if only the minor version was changed or so?
Martin,
a couple of thoughts:
1. One way to accomplish your task (i.e. upgrade the connector bundle
version in an existing connector instance) without being forced to
re-define all the components named above would have been to export the
configuration as XML, make the necessary correction and then re-import
the modified content.xml.
I agree that this is not "production-ready" but it mostly fits in a dev
scenario.
2. Allowing to change the bundle of an existing connector instance would
be quite hard to deal with, mainly because each version of any bundle
has its own specific configuration.
Instead, we could allow to change the connector instance of an existing
resource, or even to have resources without any connector instance
associated: this should go in the direction we are currently discussing
at [1].
Regards.
[1]
http://syncope-user.1051894.n5.nabble.com/quot-Virtual-quot-resources-resources-not-tied-to-an-actual-application-or-system-account-td5706735.html
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Re: csvdir connector
Posted by Martin van Es <mr...@gmail.com>.
Hi Francesco,
On Wed, Oct 17, 2012 at 6:04 PM, Francesco Chicchiriccò
<il...@apache.org> wrote:
> FYI, CSVDir connector bundle 0.5 (including this fix) was released
> yesterday: I've updated the SNAPSHOT versions to include it.
Thx for the quick fix!
Dropped the csvdir 0.5 jar in my bundles dir and it works. One remark however:
It's a PITA to deploy this new connector because I can not reassign a
new bundle to an existing connector, nor was I able to assign a
different connector to an existing resource. I even had to reconstruct
my synchronisation task!
I realise this scenario is not likely to happen in production, but I
don't want to think about the complications of un- and re-assigning
10.000+ resources to my population just because a critical bug or
feature xyz was fixed in some back-end driver?! Maybe we could at
least think of a way to allow reassigning connector bundles if only
the minor version was changed or so?
Best regards,
Martin
Re: csvdir connector
Posted by Francesco Chicchiriccò <il...@apache.org>.
Il 15/10/2012 10:38, Francesco Chicchiriccò ha scritto:
> On 12/10/2012 22:24, Martin van Es wrote:
>> Hi,
>>
>> My name is Martin and I'm making my first steps into Syncope. In line of my expertise as an Identity Manager (NetIQ) consultant, my first goal is just to experiment and see what it can do and so far I was able to setup syncope + ldap. Now however I'd like to sync the accounts to CSV file just for simple reason of inspection of the synchronisation result and fun.
>>
>> I configured the csvdir connector to contain several columns and assigned one of them to the keyColumnNames (uname). In the resources tab I carefuly configured the Username to be mapped as AccountId (which is the equivalent of "uname becomes username" as far as I understand the LDAP example. The rest of the colums are assigned arbitrary values. I am able to succesfully sync the user to csv but, the username never gets synced to the file. The contents perfectly reflect the user details, except for the username (which is key) and
>> is set to "null". And thus I can't retrieve status information of the user and after reconciliation I get a new user "null" added to the repository.
> Hi Martin,
> first of all, thanks for your interest in Syncope!
>
>> Questions:
>> Is the csvdir connector broken, or do I miss something?
> I've just tried to replicate your setup and got the same problem: opened
> [1] for this - please start it if you want to get notified.
FYI, CSVDir connector bundle 0.5 (including this fix) was released
yesterday: I've updated the SNAPSHOT versions to include it.
Regards.
>> What would be the correct setting for "Account link" in the csvdir
>> connector? I've set it to anything ranging from empty to 'uname=' +
>> username, but nothing happens to the Account Link column of the
>> account after synchronisation (it always shows an empty string, where
>> the LDAP resource shows uid=foobar,ou=people,dc=foo,dc=nl).
> 'AccountLink' is (currently) only meaningful for LDAP and
> ActiveDirectory connector bundles but might cause misbehaviours when
> valued for other connector bundles: I've opened SYNCOPE-221 for this.
>
> Short tip: leave it empty for any connector bundle but LDAP or AD.
>
> Regards.
>
> [1] https://code.google.com/p/connid/issues/detail?id=51
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Re: csvdir connector
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 12/10/2012 22:24, Martin van Es wrote:
> Hi,
>
> My name is Martin and I'm making my first steps into Syncope. In line of my expertise as an Identity Manager (NetIQ) consultant, my first goal is just to experiment and see what it can do and so far I was able to setup syncope + ldap. Now however I'd like to sync the accounts to CSV file just for simple reason of inspection of the synchronisation result and fun.
>
> I configured the csvdir connector to contain several columns and assigned one of them to the keyColumnNames (uname). In the resources tab I carefuly configured the Username to be mapped as AccountId (which is the equivalent of "uname becomes username" as far as I understand the LDAP example. The rest of the colums are assigned arbitrary values. I am able to succesfully sync the user to csv but, the username never gets synced to the file. The contents perfectly reflect the user details, except for the username (which is key) and
> is set to "null". And thus I can't retrieve status information of the user and after reconciliation I get a new user "null" added to the repository.
Hi Martin,
first of all, thanks for your interest in Syncope!
> Questions:
> Is the csvdir connector broken, or do I miss something?
I've just tried to replicate your setup and got the same problem: opened
[1] for this - please start it if you want to get notified.
> What would be the correct setting for "Account link" in the csvdir
> connector? I've set it to anything ranging from empty to 'uname=' +
> username, but nothing happens to the Account Link column of the
> account after synchronisation (it always shows an empty string, where
> the LDAP resource shows uid=foobar,ou=people,dc=foo,dc=nl).
'AccountLink' is (currently) only meaningful for LDAP and
ActiveDirectory connector bundles but might cause misbehaviours when
valued for other connector bundles: I've opened SYNCOPE-221 for this.
Short tip: leave it empty for any connector bundle but LDAP or AD.
Regards.
[1] https://code.google.com/p/connid/issues/detail?id=51
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/