[midPoint] Error while Synchronization

Thu Apr 10 21:46:52 CEST 2014

Hi Ivan,

It was because of I have not specified the inbound mappings so it was not getting synchronized from DB table to Midpoint.after doing so DB table to midpoint and midpoint to DB table is getting synchronized.

However still midpoint to LDAP is not getting synchronized,
Can you please let me know how exactly midpoint works .As per my understanding midpoint works as below

After all the configurations and tasks are in place [live synchronization] once any change in the DB table[based on the changelogColumn which is timestamp] midpoint detects the change and synchronizes the change from DB to Midpoint database

Once this is done it will synchronize from Midpoint to Ldap is this understanding correct or do we need to configure another live synchronization tasks which synchronizes from midpoint to LDAP

Can you please clear my understanding

Regards,
Nitin
From: midpoint-bounces at lists.evolveum.com [mailto:midpoint-bounces at lists.evolveum.com] On Behalf Of Nitin G. Prabhu
Sent: 10 April 2014 20:13
To: midPoint General Discussion
Subject: Re: [midPoint] Error while Synchronization

Thanks a lot Ivan for such a nice explanation. Now all the tasks are running fine but still DB table  to LDAP is not synchronizing.

All users in DB[4 users got created in midpoint which were in DB] are getting reflected in Midpoint but only name field is getting populated all other fields[first name and last name]even though mapping is present is not getting mapped

I have both resource xml files which I am using for DB table and LDAP.

Can you please let me know if anything is wrong with the configuration

[cid:image002.png at 01CF54FE.00AB81E0]

Regards,
Nitin

From: midpoint-bounces at lists.evolveum.com<mailto:midpoint-bounces at lists.evolveum.com> [mailto:midpoint-bounces at lists.evolveum.com] On Behalf Of Ivan Noris
Sent: 10 April 2014 19:34
To: midpoint at lists.evolveum.com<mailto:midpoint at lists.evolveum.com>
Subject: Re: [midPoint] Error while Synchronization

Hi Nitin,

I believe this error is caused by a missing user/name property after your user is synchronized and should be created in midPoint. This property is null.

If there is no user/name (i.e. name attribute of the new user) the synchronization cannot create user.

I don't know what resource object are you using, but this is typically because you're missing <inbound> on resource attribute that has <target>user/name</target>.

Typically this is the unique attribute of the source resource that is to become the user/name in midPoint.

                                <attribute>
                                        <ref>icfs:name</ref>
                                        <!-- Readable name for the attribute. This will be used in GUI -->
                                        <displayName>Name</displayName>
                                        <limitations>
                                                <minOccurs>0</minOccurs>
                                                <access>
                                                        <create>true</create>
                                                        <read>true</read>
                                                        <update>true</update>
                                                </access>
                                        </limitations>
                                        <inbound>
                                                <target>
                                                        <path>$user/name</path>
                                                </target>
                                        </inbound>
                                </attribute>

... this is from our sample localhost-dbtable-advanced-sync.xml - I'm sure you have seen it before. The icfs:name (corresponding to dbtable attribute configured as keyColumn) will be synced to user/name attribute.

To make it short, and useful for other in similar situation:

The synchronization must succeed in the following steps to create new user from resource account:
1. synchronization must be configured (<synchronization> section)
2. for livesync, LiveSync task must be running
3. correlation rule must be in resource <synchronization> section
4. reaction for "unmatched" situation must be set to "addUser"
5. at least user/name attribute must be filled during synchronization by inbound expression (see above).
6. password must be generated for new midPoint user during synchronization by inbound expression (<generate/> - as answered earlier today)

Hope this helps.

Regards,
Ivan
On 04/10/2014 04:53 PM, Nitin G. Prabhu wrote:
Hi ,

Resolved the below issue by changing the default password configuration.

But now getting below error .I am missing any configuration

Internal Error: Synchronization error: com.evolveum.midpoint.util.exception.SystemException: Synchronization action failed, reason: Focus UserType:null(null) does not have a name after inbound and user policy

Regards,
Nitin
From: midpoint-bounces at lists.evolveum.com<mailto:midpoint-bounces at lists.evolveum.com> [mailto:midpoint-bounces at lists.evolveum.com] On Behalf Of Nitin G. Prabhu
Sent: 10 April 2014 15:04
To: midPoint General Discussion
Subject: Re: [midPoint] Error while Synchronization

Thanks Ivan,

That issue is resolved now but now I am getting below error.

[cid:image003.png at 01CF54FE.00AB81E0]

-----Original Message-----
From: midpoint-bounces at lists.evolveum.com<mailto:midpoint-bounces at lists.evolveum.com> [mailto:midpoint-bounces at lists.evolveum.com] On Behalf Of Ivan Noris
Sent: 10 April 2014 14:37
To: midpoint at lists.evolveum.com<mailto:midpoint at lists.evolveum.com>
Subject: [midPoint] Error while Synchronization

Hi Nitin,

you get "Found more than one account with the identifier..." error because livesync thinks there are multiple accounts with to-be-unique attribute "uid".

If this is DB Table: Please check the "keyColumn" configuration parameter in your db table resource. It seems you have configured this incorrectly...

Regarding your problem with "timestamp" type, can you please post how your database table was constructed so that we can replicate this?

Regards,

Ivan

--

  Ing. Ivan Noris

     IT Architect

  nLight, s.r.o.

  ___________________________________________________

  "Semper cautus - semper paratus - semper idem Vix."

_______________________________________________

midPoint mailing list

midPoint at lists.evolveum.com<mailto:midPoint at lists.evolveum.com>

http://lists.evolveum.com/mailman/listinfo/midpoint

MASTEK LTD.
In the US, we're called MAJESCOMASTEK

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them. If you have received this e-mail in error, kindly delete this e-mail from desktop and server.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

MASTEK LTD.
In the US, we're called MAJESCOMASTEK

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them. If you have received this e-mail in error, kindly delete this e-mail from desktop and server.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

_______________________________________________

midPoint mailing list

midPoint at lists.evolveum.com<mailto:midPoint at lists.evolveum.com>

http://lists.evolveum.com/mailman/listinfo/midpoint

--

  Ing. Ivan Noris

  Senior Identity Management Engineer

  evolveum.com

  ___________________________________________

           "Idem per idem - semper idem Vix."

MASTEK LTD.
In the US, we're called MAJESCOMASTEK

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them. If you have received this e-mail in error, kindly delete this e-mail from desktop and server.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

MASTEK LTD.
In the US, we're called MAJESCOMASTEK

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them. If you have received this e-mail in error, kindly delete this e-mail from desktop and server.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20140411/a4a7a8b8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 36451 bytes
Desc: image002.png
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20140411/a4a7a8b8/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 34202 bytes
Desc: image003.png
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20140411/a4a7a8b8/attachment-0001.png>