[
https://issues.apache.org/jira/browse/DIRSERVER-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865124#action_12865124
]
Stefan Seelmann commented on DIRSERVER-1497:
--------------------------------------------
It would also be nice to define such referrals per operation or at least for
read and/or write operations. This way it would be possible to define read-only
shadow servers and redirect all write operations to the master server.
<jdbmPartition id="example"
suffix="dc=example,dc=com"
writeReferral="ldap://example.com:489";...>
> We need to support DSA referrals
> --------------------------------
>
> Key: DIRSERVER-1497
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1497
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.7
> Reporter: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0.0-RC1
>
>
> Atm, we just support 'smart' referrals (ie, referrals handled in entries), we
> don't support DSA referrals (or suffix referrals).
> This is a must have : we should be able to redirect all request to another
> server if the requested DN does not exist in the local DIT, or we should be
> able to do the same thing if the current server is in maintenance mode.
> This kind of referral must be configured globally, and handled globally. We
> can add a referral with each suffix, plus a global one.
> For instance, a global referral can be set this way :
> <defaultDirectoryService id="directoryService" instanceId="default"
> referral="ldap://remote.server:389";
> referralActivated="false"
> ...
> so that if we change the flag to TRUE, any request will be redirected to the
> remote server.
> For the suffix referral, we can do that :
> <jdbmPartition id="example"
> suffix="dc=example,dc=com"
> referral="ldap://example.com:489";...>
> then any request done on dc=example,dc=com will be redirected on the
> example.com server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
