Re: FW: (ITS#5941) Problem when stacking rwm and translucent overlays together

Wednesday, 6 October 2010

--=-J3E4Om04oCzTAxqDTGlw
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

...
 In the meanwhile, you can try to use an instance of back-ldap as the
 translucent local storage, and place slapo-rwm on the database of the
 remote server that acts as local.  I haven't tested it, so there might be
 minor issues, but I don't expect anything like this one. 
Thanks for the input.
This is also not an option because the remote server is in fact an Active Directory.
Which in this case I can't alter.

I will try to create 2 slapd process
 - One which will do the translucent proxy stuff, running on a non standard port
 - one which will have a back-ldap to this non standard port and doing there the
rewrites.

Thanks for helping me with this issue.

--=-J3E4Om04oCzTAxqDTGlw
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html;
CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.28.3">
</HEAD>
<BODY>
<PRE>
&gt; In the meanwhile, you can try to use an instance of back-ldap as the
&gt; translucent local storage, and place slapo-rwm on the database of the
&gt; remote server that acts as local.&nbsp; I haven't tested it, so there
might be
&gt; minor issues, but I don't expect anything like this one.

Thanks for the input.
This is also not an option because the remote server is in fact an Active Directory.
Which in this case I can't alter.

I will try to create 2 slapd process
 - One which will do the translucent proxy stuff, running on a non standard port
 - one which will have a back-ldap to this non standard port and doing there the
rewrites.

Thanks for helping me with this issue.

</PRE>
<BR>
</BODY>
</HTML>

--=-J3E4Om04oCzTAxqDTGlw--

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006