[
https://issues.apache.org/jira/browse/KNOX-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833549#comment-15833549
]
Larry McCay commented on KNOX-861:
----------------------------------
[~kamrul] - this sounds like a great improvement.
A couple tips for making this a purely custom mechanism for circumstances where
the validator cannot be contributed to the community - which I think is
probably important here.
1. Jars containing the validator would be added to the {GATEWAY_HOME}/ext
directory which will put them on the classpath
2. The PreAuthValidator interface could be used to discover validator impls
from the classpath using the java ServiceLoader mechanism
3. The configured name within the topology would then be used to disambiguate
the implementation to use - since there will be more than one
4. The existing IpValidator and DefaultValidator should be added to the same
ServiceLoader mechanism as well - just add a file to the
resources/META_INF/services directory for that interface that has those two
classnames in it - just as exists for the contributor interface there already
> Support pluggable validator for Header pre authentication provider
> -------------------------------------------------------------------
>
> Key: KNOX-861
> URL: https://issues.apache.org/jira/browse/KNOX-861
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Mohammad Kamrul Islam
> Assignee: Mohammad Kamrul Islam
> Fix For: 0.12.0
>
>
> Currently there are two validators : IPValidator, DefaultValidator,
> IPValidator validates the source IP. DefaultValidator is basically a
> no-auth.
> The proposal is to provide a pluggable validator to support any custom
> validation logic. Another requirement is to maintain the backward
> compatibility of any existing features.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
