[midPoint] Midpoind connect mysql DB

mceylan mrveceylan at gmail.com
Mon Jun 6 11:07:37 CEST 2016


Hi Ivan,

I use to connect to localhost db-table on a redmine. Midpoint resource list
Localhost DB table succesfull connect.

Users-list users-select user (merve)- add projection-select Localhost
DBTable add resources.



  Localhost DBTable
admin

auth_source_id

created_on

First name

id *

identity_url

language

Last name

last_login_on

mail_notification

must_change_passwd

Name

passwd_changed_on

salt

status *

type

updated_on

association





id and status filled and save. mysqldb users tables creating users (merve).
But  redmine users list not creating users(merve).


















2016-06-06 11:46 GMT+03:00 Ivan Noris <ivan.noris at evolveum.com>:

> Hi Merve,
>
> I would like to understand what are you trying to achieve, what were your
> steps on redmine side and how you configured midPoint DBTable resource. The
> idm.log you sent unfortunately does not contain anything regarding DBTable
> connector/provisioning...
>
> I don't know/use redmine, so I need to understand the environment.
>
> Regards,
> Ivan
>
>
> On 06/06/2016 10:09 AM, mceylan wrote:
>
>
> Hi ivan,  no problem users add resources localhost db table. I  have a
> problem mysql db in users creating redmine users list
>
>
> idm. log
>
>
> 2016-06-06 10:50:07,763 [REPOSITORY] [midPointScheduler_Worker-7] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 10:50:08,002 [REPOSITORY] [midPointScheduler_Worker-7] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 10:50:08,228 [REPOSITORY] [midPointScheduler_Worker-6] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 10:50:08,453 [REPOSITORY] [midPointScheduler_Worker-7] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 10:50:08,666 [REPOSITORY] [midPointScheduler_Worker-6] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 10:50:08,891 [REPOSITORY] [midPointScheduler_Worker-7] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 10:50:09,080 [REPOSITORY] [midPointScheduler_Worker-7] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 10:50:09,081 [REPOSITORY] [midPointScheduler_Worker-6] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 10:50:09,379 [REPOSITORY] [midPointScheduler_Worker-6] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 11:05:07,767 [REPOSITORY] [midPointScheduler_Worker-10] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 11:05:07,982 [REPOSITORY] [midPointScheduler_Worker-1] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 11:05:08,205 [REPOSITORY] [midPointScheduler_Worker-10] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 11:05:08,445 [REPOSITORY] [midPointScheduler_Worker-1] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 11:05:08,657 [REPOSITORY] [midPointScheduler_Worker-10] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 11:05:08,869 [REPOSITORY] [midPointScheduler_Worker-1] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 11:05:09,090 [REPOSITORY] [midPointScheduler_Worker-10] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> 2016-06-06 11:07:03,853 [MODEL] [Thread-19] WARN
> (com.evolveum.midpoint.model.impl.lens.projector.ReconciliationProcessor):
> Can't do reconciliation. Account context doesn't contain current version of
> account.
> 2016-06-06 11:07:04,492 [REPOSITORY] [ClusterManagerThread] INFO
> (org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl): HHH000010: On
> release of batch it still contained JDBC statements
> ~
>
>
>
> 2016-06-06 11:04 GMT+03:00 Ivan Noris <ivan.noris at evolveum.com>:
>
>> Please paste error exception from idm.log.
>>
>> Ivan
>>
>>
>> On 06/06/2016 09:48 AM, mceylan wrote:
>>
>> Thanks Ivan. I connect midpoint mysql db. add users mysql db but i add
>> user not creating redmine.
>>
>> Can you help me?
>>
>> 2016-06-06 10:24 GMT+03:00 Ivan Noris < <ivan.noris at evolveum.com>
>> ivan.noris at evolveum.com>:
>>
>>> Hi Merve,
>>>
>>> Ah, so you are trying to connect midPoint to existing application
>>> (redmine) with the DBTable connector, right?
>>> This could work, if:
>>>
>>> 1) the existing application is using only one table
>>> 2) if you have created technical user to connect using the connector (as
>>> Test connection works for you, you have at least some permissions)
>>> 3) the localhost-dbtable-advanced-sync.xml is a sample for the database
>>> table with fixed columns as created in the *.sql file(s) in the
>>> samples/resources/databasetable directory. So you need to modify your
>>> schema handling to use correct attributes for your application database
>>> table, not for our samples.
>>>
>>> Specifically it seems that your database has no "enable/disable" status
>>> attribute. In our sample, we have two configuration elements for
>>> enable/disable:
>>>
>>> 1) capabilities: defines which database table attribute is used for
>>> enable/disable. In our samples it's attribute/column named "disabled". If
>>> your database table has different column for this, it must be defined here
>>> or removed the section if your db does not support it.
>>>                 <capabilities xmlns:cap=
>>> <http://midpoint.evolveum.com/xml/ns/public/resource/capabilities-3>
>>> "http://midpoint.evolveum.com/xml/ns/public/resource/capabilities-3"
>>> <http://midpoint.evolveum.com/xml/ns/public/resource/capabilities-3>>
>>>                         <configured>
>>>                                 <cap:activation>
>>>                                         <cap:status>
>>>                                                 <cap:attribute>
>>> *ri:disabled*</cap:attribute>
>>>
>>> <cap:enableValue></cap:enableValue>
>>>
>>> <cap:enableValue>false</cap:enableValue>
>>>
>>> <cap:disableValue>true</cap:disableValue>
>>>                                         </cap:status>
>>>                                 </cap:activation>
>>>                         </configured>
>>>                 </capabilities>
>>>
>>> 2) activation/administrativeStatus mapping: defines how enable/disable
>>> in midPoint goes to the databasetable (outbound) or vice versa (inbound).
>>> If your db table does not support this, remove/comment this mapping:
>>>
>>>                                 <activation>
>>>                                         <administrativeStatus>
>>>                                                 <outbound/>
>>>                                                 <inbound>
>>>
>>> <strength>weak</strength>
>>>                                                 </inbound>
>>>                                         </administrativeStatus>
>>>                                 </activation>
>>>
>>> Best regards,
>>> Ivan
>>>
>>>
>>> On 06/04/2016 09:03 PM, <mrveceylan at gmail.com>mrveceylan at gmail.com
>>> wrote:
>>>
>>> I dont now. I want to midpoint connection redmine
>>>
>>> iPhone'umdan gönderildi
>>>
>>> 3 Haz 2016 tarihinde 17:58 saatinde, Ivan Noris <
>>> <ivan.noris at evolveum.com>ivan.noris at evolveum.com> şunları yazdı:
>>>
>>> Hi Merve,
>>>
>>> which SQL creation script have you used to create the MySQL table?
>>> Ivan
>>>
>>> On 06/03/2016 03:40 PM, mceylan wrote:
>>>
>>> Hi,
>>>
>>> Midpoint connection mysql dbtable. I using file
>>> locolhost-dbtable--advanced-sync.xml
>>> Midpoint connection succesfull mysql db.
>>>
>>> Midpoint users add resource localhost DBTable
>>>
>>> stack tree
>>>
>>>
>>> Couldn't add object. Schema violation: Schema violation during
>>> processing shadow: shadow: null (OID:null): DB syntax error:
>>> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException(Unknown column
>>> '__ENABLE__' in 'field list')
>>>
>>>
>>>    -
>>>
>>> --
>>>
>>> can you help me?
>>> Merve CEYLAN
>>>
>>>
>>> _______________________________________________
>>> midPoint mailing listmidPoint at lists.evolveum.comhttp://lists.evolveum.com/mailman/listinfo/midpoint
>>>
>>>
>>> --
>>>   Ing. Ivan Noris
>>>   Senior Identity Management Engineer & IDM Architect
>>>   evolveum.com                     evolveum.com/blog/
>>>   ___________________________________________________
>>>   "Semper ID(e)M Vix."
>>>
>>> _______________________________________________
>>> midPoint mailing list
>>> midPoint at lists.evolveum.com
>>> http://lists.evolveum.com/mailman/listinfo/midpoint
>>>
>>>
>>>
>>> _______________________________________________
>>> midPoint mailing listmidPoint at lists.evolveum.comhttp://lists.evolveum.com/mailman/listinfo/midpoint
>>>
>>>
>>> --
>>>   Ing. Ivan Noris
>>>   Senior Identity Management Engineer & IDM Architect
>>>   evolveum.com                     evolveum.com/blog/
>>>   ___________________________________________________
>>>   "Semper ID(e)M Vix."
>>>
>>>
>>> _______________________________________________
>>> midPoint mailing list
>>> midPoint at lists.evolveum.com
>>> http://lists.evolveum.com/mailman/listinfo/midpoint
>>>
>>>
>>
>>
>> --
>> Merve CEYLAN
>>
>>
>> _______________________________________________
>> midPoint mailing listmidPoint at lists.evolveum.comhttp://lists.evolveum.com/mailman/listinfo/midpoint
>>
>>
>> --
>>   Ing. Ivan Noris
>>   Senior Identity Management Engineer & IDM Architect
>>   evolveum.com                     evolveum.com/blog/
>>   ___________________________________________________
>>   "Semper ID(e)M Vix."
>>
>>
>> _______________________________________________
>> midPoint mailing list
>> midPoint at lists.evolveum.com
>> http://lists.evolveum.com/mailman/listinfo/midpoint
>>
>>
>
>
> --
> Merve CEYLAN
>
>
> _______________________________________________
> midPoint mailing listmidPoint at lists.evolveum.comhttp://lists.evolveum.com/mailman/listinfo/midpoint
>
>
> --
>   Ing. Ivan Noris
>   Senior Identity Management Engineer & IDM Architect
>   evolveum.com                     evolveum.com/blog/
>   ___________________________________________________
>   "Semper ID(e)M Vix."
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>


-- 
Merve CEYLAN
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20160606/8eaebf16/attachment.htm>


More information about the midPoint mailing list