[midPoint] dirsync cookie size

Andrew Morgan morgan at oregonstate.edu
Sat Sep 15 22:43:27 CEST 2018


Thanks!  I would appreciate this fix being backported to v3.8, if 
possible.

Pavol, you are doing some great work!

Andy Morgan
Systems Administrator, Identity & Access Management
Information Services | Oregon State University
541-737-8877 | is.oregonstate.edu

On Sat, 15 Sep 2018, Pavol Mederly wrote:

> Hello Davy, Andrew,
>
> it is fixed in v3.9devel-810-g6ad3f2d. Took some time because there is really a lot of work these days.
>
> Davy, you say it blocks your deployment. Does this mean you need this patch to be backported to support-3.8 branch?
>
> Best regards,
>
> Pavol Mederly
> Software developer
> evolveum.com
>
>
> On 07.09.2018 21:25, Davy Priem wrote:
> Hi Andrew,
>
> I wanted to enable AD live sync on our production env and I got the same issue. I’ve created https://jira.evolveum.com/browse/MID-4878 since this blocks our deployment.
>
> Davy Priem
> IT technical management
>
> VIVES University of Applied Sciences | Dienst IT
> Doorniksesteenweg 145 | 8500 Kortrijk
>
>
> Op 4 sep. 2018, om 02:09 heeft Andrew Morgan <morgan at oregonstate.edu<mailto:morgan at oregonstate.edu>> het volgende geschreven:
>
> I want to use LiveSync against Active Directory.  I tested this against a DEV AD forest successfully.  However, our production AD forest sends back a dirsync cookie that is too large to store in the database.  Here is the error message:
>
> Caused by: java.sql.BatchUpdateException: (conn:2031) Data too long for column 'stringValue' at row 1
> Query is: insert into m_object_ext_string (item_id, owner_oid, ownerType, stringValue) values (?, ?, ?, ?), parameters [3,'f82fdd36-4c48-4fb6-a63a-41b7a4c3d87c',0,'TVN
> EUwMAAAAnXGd2x0LUAQAAAAAAAAAAYAEAAKtAqxsAAAAAAAAAAAAAAACrQKsbAAAAAHPlzWqF1FtDm1ZrUmr4u/MBAAAAAAAAAA4AAAAAAAAAhqWdCK+vK02geidsZEcwPLtShAEAAAAArof1HJPRtky2F91ymoTezNjxBg
> AAAAAA46GJMRVAcU2tKRkmqVaV1J+dagAAAAAAcrUjMp5l50+jD8wFx6wJJjHD2xIAAAAAdpm4VNLlFka4g0XbrKotWMDcdgEAAAAAWKaYVZylhU6lcupRoF3dJ2Gu8xwAAAAAGuwbW5pZ9Uyj9C51G+Cn+XAreCwAAAAAc
> +XNaoXUW0ObVmtSavi788RAqxsAAAAAFP87ecztkkC/rUXsZKbD3DJFlC8AAAAAQSkin09ZxEuR3AkpCse6hldb+AIAAAAAZTmHyMWZlEip9Ud4ctmZQcz3AAAAAAAApJnX7Zy8A0KPlWzyWh3+kBnSbAAAAAAAjuvm8MeE
> 6UOQ5G8LLXFnsb/YBQAAAAAAoalZ8hHbSUiEDZ030itBSixrzQEAAAAA']
>
> stringValue is varchar(191), but the dirsync cooke is huge - 560 characters long.
>
> Is this a known issue?
>
> Thanks,
>
> Andy Morgan
> Systems Administrator, Identity & Access Management
> Information Services | Oregon State University
> 541-737-8877 | is.oregonstate.edu<http://is.oregonstate.edu>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com<mailto:midPoint at lists.evolveum.com>
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com<mailto:midPoint at lists.evolveum.com>
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
>


More information about the midPoint mailing list