On 15/03/2012 12:17, ernst Developer wrote:
That is a tricky one: 0.5.2 
Wow, this is definitely old: too may things have changed in the
meanwhile...
I can only suggest to update as soon as possible to latest stable
(0.7.1) or. even better, to latest snapshot of Apache Syncope,
otherwise it would be rather impossible for anyone here to provide
any support.
Regards.
2012/3/15 Francesco Chicchiriccò <[email protected]>
On 15/03/2012 12:08, ernst Developer wrote:
Hi,
We are using Syncope with AD Connector with synchronize
capability.
The SN is mapped to a schema field, and for this field
the mandatory condition is set to true.
In AD exists a user without a value for SN. I expect
that when this user is picked up by the AD connector,
the insert into Syncope fails, because of the missing SN
(this field is set to mandatory in the mapping).
What I see is that the user is created in Syncope, and
gets provisioned. The provisioning fails, because the
surname is mandatory in for instance the Google apps
connector. At the end the user does not exist in
Syncope.
My questions are:
* is the mandatory field checked on synchronization?
* if this property is not checked on synchronization,
how can I prevent that this user is created?
Hi Ernst,
which version are you running?
--
Francesco Chicchiriccò
Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
|
