Fedora directory users - Mar 2006 - Directory Express...customize? separate/relocate?

I have been looking at Directory Express pages on our new setup.  Very 
nice!  I have a few questions:

I''ll need to make a few schema extensions for some attributes that will
be set on a do-it-yourself basis (using Directory Express, I hope).  Is 
there any sort of guide to customizing Directory Express in such a way 
that changes will be preserved during future upgrades?  I''ve rummaged 
aound in /var/opt/fedora-ds/clients/dsgw to get a sense of the layout, 
but didn''t know if there was a systematic guide of sorts.

(I could probably figure this next one out with more rummaging, but one 
of you might provide a quick "Don''t even bother!" answer)...

Is it feasible to move/separate the Directory Express components so that 
they could run on a server separate from the admin server?   What I have 
in place is an intranet server running under PubCookie.  My thought is 
to put "DE" under this existing PubCookie regime and take advantage of
stuff like REMOTE_USER vars.  Just not sure if that is doable.  I also 
started to look at moving the Fedora-DS httpd.worker under PubCookie, 
but that would seem  more dubious.

Thanks!

Jim
 

  

-- 
/*********************************************************/
 Jim Hogan                 
/*********************************************************/

Jim Hogan wrote:
> I have been looking at Directory Express pages on our new setup.  Very 
> nice!  I have a few questions:
>
> I''ll need to make a few schema extensions for some attributes that
> will be set on a do-it-yourself basis (using Directory Express, I 
> hope).  Is there any sort of guide to customizing Directory Express in 
> such a way that changes will be preserved during future upgrades?  
> I''ve rummaged aound in /var/opt/fedora-ds/clients/dsgw to get a
sense
> of the layout, but didn''t know if there was a systematic guide of
sorts.
http://www.redhat.com/docs/manuals/dir-server/pdf/ds71gwcust.pdf
>
> (I could probably figure this next one out with more rummaging, but 
> one of you might provide a quick "Don''t even bother!"
answer)...
>
> Is it feasible to move/separate the Directory Express components so 
> that they could run on a server separate from the admin server?   What 
> I have in place is an intranet server running under PubCookie.  My 
> thought is to put "DE" under this existing PubCookie regime and
take
> advantage of stuff like REMOTE_USER vars.  Just not sure if that is 
> doable.  I also started to look at moving the Fedora-DS httpd.worker 
> under PubCookie, but that would seem  more dubious.
I assume PubCookie is some sort of SSO thing?  The DE stuff uses it''s 
own cookie scheme - you''d probably have to hack the source code.
>
> Thanks!
>
> Jim
>
>
>  
>

Richard Megginson wrote:
> Jim Hogan wrote:
>
>> [...] Is there any sort of guide to customizing Directory Express in 
>> such a way that changes will be preserved during future upgrades?  
>> I''ve rummaged aound in /var/opt/fedora-ds/clients/dsgw to get
a sense
>> of the layout, but didn''t know if there was a systematic guide
of sorts.
>
> http://www.redhat.com/docs/manuals/dir-server/pdf/ds71gwcust.pdf
Ah, thanks.  I just bookmarked that "dir-server" doc page.
>>
>> [...] I also started to look at moving the Fedora-DS httpd.worker 
>> under PubCookie, but that would seem  more dubious.
>
> I assume PubCookie is some sort of SSO thing?  
Yes, www.pubcookie.org.  Produced by the folks here.  Very nice, pretty 
simple to implement (at least when the parent organization already has 
has the server service in place!)
> The DE stuff uses it''s own cookie scheme - you''d probably
have to hack
> the source code.
This tells me that option #2 -- moving the DS httpd.worker under 
PubCookie would be just as onerous.  I think I''ll save this goal for 
later :)

Thanks,

Jim
>
>>
>> Thanks!
>>
>> Jim
>>
>>
>>  
>>
>------------------------------------------------------------------------
>
>--
>Fedora-directory-users mailing list
>Fedora-directory-users@redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-directory-users
>  
>

-- 
/*********************************************************/
 Jim Hogan          
/*********************************************************/

I had another thought on this thread....

Our FDS directory will be essentially for internal use, and we only want 
to expose it enough for some of our people to update their records 
through a Web page that pre-authenticates/authorizes them (our PubCookie 
scheme).

Rather than try to separate the DE code onto this server, one thought I 
had last night was to set up a reverse proxy on our PubCookie''s portal 
server that proxies the DE pages.  Not sure how this will work out with 
the 2 different cookie regimes.

This notion isn''t particularly germane to the Fedora Directory Server 
lists, but I figured I''d throw it up here on the list in case someone 
has already been/done and can offer an opinion.  Otherwise, if I try it 
and it works, I''ll let you know!

Jim

Richard Megginson wrote:
> Jim Hogan wrote:
>
>>  My thought is to put "DE" under this existing PubCookie
regime and
>> take advantage of stuff like REMOTE_USER vars.  Just not sure if that 
>> is doable.  I also started to look at moving the Fedora-DS 
>> httpd.worker under PubCookie, but that would seem  more dubious.
>
>
> I assume PubCookie is some sort of SSO thing?  The DE stuff uses
it''s
> own cookie scheme - you''d probably have to hack the source code.
>
>>
>> Thanks!
>>
>> Jim
>>
>>
>>  
>>
>------------------------------------------------------------------------
>
>--
>Fedora-directory-users mailing list
>Fedora-directory-users@redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-directory-users
>  
>

-- 
/*********************************************************/
 Jim Hogan       
/*********************************************************/