[prev in list] [next in list] [prev in thread] [next in thread]
List: forgerock-openidm
Subject: Re: [OpenIDM] Provisioning between two openIDM's
From: Andreas Egloff <andi.egloff () forgerock ! com>
Date: 2015-02-19 18:11:30
Message-ID: CALto_tzTkSR11m2RwWgz2x0L94VqJ9A1sMoVm-2=p3UpJ6K77A () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Or you could use the onCreate/onUpdate/onDelete hooks to write your own
change log in repo/, and poll that.
On Thu, Feb 19, 2015 at 7:07 PM, Jake Feasel <jake.feasel@forgerock.com>
wrote:
> There isn't a built-in changelog mechanism in OpenIDM, however it would be
> fairly simple to implement one. You would just need to add a timestamp
> column on your managed/ objects, and make sure that it gets updated with
> each change (onCreate and onUpdate script handlers within managed.json
> should work fine). Then to find the latest changes, you would just need a
> query that looks for records which have timestamp values greater then the
> last time you checked (as represented by the livesync token).
>
> On Wed, Feb 18, 2015 at 9:17 AM, Fabien <fdemarest@deloitte.com> wrote:
>
> > Matthias Tristl wrote
> > > You are missing ?_queryId=query-all-ids in your request:
> > > system/scriptedcrest/users?_queryId=query-all-ids
> > > is the full query
> > >
> > > Matthias
> >
> > I was just mentioning that action as an example, not the request itself :)
> >
> > Anyway, *I managed to get the CREST connector working between two
> > OpenIDM's*
> > by capturing the output of the OpenICF connector and playing around with
> > the
> > groovy TestScript.
> >
> > The provisioner and mapping I have now manage reconciliation without a
> > problem (including passwords, account status, ...). The next step is to
> > customize the groovy scripts to *get LiveSync working.*
> >
> > As I mentioned earlier, my configuration is based on the CREST sample with
> > OpenDJ. OpenDJ works with a changelog to check for changes on the target,
> > so
> > obvious LiveSync doesn't work out-of-the-box.
> >
> > In the SyncScript.groovy of the connector for OpenDJ I can see :
> >
> > /QueryRequest request = Requests.newQueryRequest('/changelog')
> > [...]
> > /
> >
> > What queries are needed to poll for changes on OpenIDM with OpenICF?
> >
> > How does OpenIDM exactly check for changes internally, simply with the
> > _rev
> > field, also with a timestamp or something else?
> >
> > Any help would be very appreciated.
> >
> >
> >
> > --
> > View this message in context:
> > http://openidm-users.989380.n3.nabble.com/OpenIDM-Provisioning-between-two-openIDM-s-tp4027987p4028056.html
> > Sent from the OpenIDM Users mailing list archive at Nabble.com.
> > _______________________________________________
> > OpenIDM mailing list
> > OpenIDM@forgerock.org
> > https://lists.forgerock.org/mailman/listinfo/openidm
> >
>
>
> _______________________________________________
> OpenIDM mailing list
> OpenIDM@forgerock.org
> https://lists.forgerock.org/mailman/listinfo/openidm
>
>
[Attachment #5 (text/html)]
<div dir="ltr">Or you could use the onCreate/onUpdate/onDelete hooks to write your \
own change log in repo/, and poll that.</div><div class="gmail_extra"><br><div \
class="gmail_quote">On Thu, Feb 19, 2015 at 7:07 PM, Jake Feasel <span \
dir="ltr"><<a href="mailto:jake.feasel@forgerock.com" \
target="_blank">jake.feasel@forgerock.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">There isn't a built-in changelog mechanism \
in OpenIDM, however it would be fairly simple to implement one. You would just need \
to add a timestamp column on your managed/ objects, and make sure that it gets \
updated with each change (onCreate and onUpdate script handlers within managed.json \
should work fine). Then to find the latest changes, you would just need a query that \
looks for records which have timestamp values greater then the last time you checked \
(as represented by the livesync token).</div><div class="HOEnZb"><div class="h5"><div \
class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 18, 2015 at 9:17 AM, \
Fabien <span dir="ltr"><<a href="mailto:fdemarest@deloitte.com" \
target="_blank">fdemarest@deloitte.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Matthias Tristl wrote<br> <span>> You are missing \
?_queryId=query-all-ids in your request:<br> > \
system/scriptedcrest/users?_queryId=query-all-ids<br> > is the full query<br>
><br>
> Matthias<br>
<br>
</span>I was just mentioning that action as an example, not the request itself :)<br>
<br>
Anyway, *I managed to get the CREST connector working between two OpenIDM's*<br>
by capturing the output of the OpenICF connector and playing around with the<br>
groovy TestScript.<br>
<br>
The provisioner and mapping I have now manage reconciliation without a<br>
problem (including passwords, account status, ...). The next step is to<br>
customize the groovy scripts to *get LiveSync working.*<br>
<br>
As I mentioned earlier, my configuration is based on the CREST sample with<br>
OpenDJ. OpenDJ works with a changelog to check for changes on the target, so<br>
obvious LiveSync doesn't work out-of-the-box.<br>
<br>
In the SyncScript.groovy of the connector for OpenDJ I can see :<br>
<br>
/QueryRequest request = Requests.newQueryRequest('/changelog')<br>
[...]<br>
/<br>
<br>
What queries are needed to poll for changes on OpenIDM with OpenICF?<br>
<br>
How does OpenIDM exactly check for changes internally, simply with the _rev<br>
field, also with a timestamp or something else?<br>
<br>
Any help would be very appreciated.<br>
<br>
<br>
<br>
--<br>
View this message in context: <a \
href="http://openidm-users.989380.n3.nabble.com/OpenIDM-Provisioning-between-two-openIDM-s-tp4027987p4028056.html" \
target="_blank">http://openidm-users.989380.n3.nabble.com/OpenIDM-Provisioning-between-two-openIDM-s-tp4027987p4028056.html</a><br>
<div><div>Sent from the OpenIDM Users mailing list archive at Nabble.com.<br>
_______________________________________________<br>
OpenIDM mailing list<br>
<a href="mailto:OpenIDM@forgerock.org" target="_blank">OpenIDM@forgerock.org</a><br>
<a href="https://lists.forgerock.org/mailman/listinfo/openidm" \
target="_blank">https://lists.forgerock.org/mailman/listinfo/openidm</a><br> \
</div></div></blockquote></div><br></div> \
</div></div><br>_______________________________________________<br> OpenIDM mailing \
list<br> <a href="mailto:OpenIDM@forgerock.org">OpenIDM@forgerock.org</a><br>
<a href="https://lists.forgerock.org/mailman/listinfo/openidm" \
target="_blank">https://lists.forgerock.org/mailman/listinfo/openidm</a><br> \
<br></blockquote></div><br></div>
_______________________________________________
OpenIDM mailing list
OpenIDM@forgerock.org
https://lists.forgerock.org/mailman/listinfo/openidm
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic