[
https://issues.apache.org/jira/browse/DIRSTUDIO-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637282#action_12637282
]
Emmanuel Lecharny commented on DIRSTUDIO-410:
---------------------------------------------
The biggest problem I see is that JNDI 'ignore' semantic is the opposite to
what you have implemented with the 'ignore' option : it always send the
ManageDsaIT control. The idea is that JNDI should 'ignore' the referral
characteristic of the entry, and just consider it as a normal entry, instead of
sending back a Referral result.
I'm afraid that those who are using Studio may be tainted by JNDI... (btw, the
'follow' option is a typical JNDI option).
Anyway, what I would suggest is that we propose something more in line with
what really happens : instead of using one word, express the referral handling
processing. Something like :
- Follow referrals
- Ignore referrals
- Ask the users (ie, throw)
wdyt ?
> Referral handling is problematic
> --------------------------------
>
> Key: DIRSTUDIO-410
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-410
> Project: Directory Studio
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Emmanuel Lecharny
> Priority: Critical
>
> The way referrals are handled in the server is problematic.
> There is a mix between JNDI and plain LDAP (ManageDsaIT control usage).
> Beside the fact that one should be able to select the way referral should be
> handled on each request (it's painful to have to disconnect when you change
> the global property), for people used to deal with JNDI, the 'manage' option
> does not make sense.More than that, 'manage' defaults to 'ignore' (which is
> plain OK, so far), but the 'ignore' option is not activated.
> I would suggest that we switch to 'ignore', 'throw' and 'follow' instead of
> 'follow', 'ignore' and 'manage'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
