Return to Jive Software

Skip navigation
1,515 Views 1 Reply Last post: Jul 13, 2009 11:43 AM by brad.heller RSS
n99 Novice 151 posts since
Dec 1, 2008
Currently Being Moderated

May 21, 2009 8:14 AM

ldap integration - group synchronization

Hello

 

We have clearspace 2.5.4 and are moving to 2.5.11 before we go live.

 

I was wondering about group synching and  http://www.jivesoftware.com/jivespace/docs/DOC-4622#How_do_I_override_lazyloading_of_group_memberships:

It looks like the spring.xml config works to run a group synch only after a clearspace restart - is that correct?

Is there anything we can configure to get it running nightly without a restart?

I ask as we have need to know about new ldap groups in clearspace before a lazy-load takes place.

 

Also

Is there another way of synchronising groups as 2 of our clearspace instances seem to have alot of heavily populated groups with numbers way beyond those that have yet logged in.

This is confusing us.

 

I can't find the spring.xml file on these systems so was wondering if there was another way(s) of getting the group synch to run gloabally?

I presume running a manual user synch won't run a group synch?

 

I found this http://www.jivesoftware.com/jivespace/message/107506#107506 - but not sure if relates to 2.5.* as I can't find the spring-managerContext.xml file.

Is the groupMember cache relevant and if so, how is it cleared out?

 

Also when using my clearspace logging in jiveHome/logs/clearspace.log, output doesn't seem to go in straight away. Is there so sort of buffer on the log?

 

 

 

Regards

 

Nomit

Expert 3,518 posts since
Jun 18, 2009
Currently Being Moderated
Jul 13, 2009 11:43 AM in response to: nomit babraa
Re: ldap integration - group synchronization

Hey there,

 

Sorry for the delayed repl here. Did you guys ever get a resolution to this?

 

Let me know and, if not, I can help out!

 

Cheers,

Brad

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.