[
https://issues.apache.org/jira/browse/KNOX-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876886#comment-15876886
]
ASF subversion and git services commented on KNOX-868:
------------------------------------------------------
Commit c346ee3798d84eb862cabda2d95d6409d7b4da0f in knox's branch
refs/heads/master from [~moresandeep]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=c346ee3 ]
KNOX-868 - Add /ext/native to java.library.path in gateway.sh (Mohammad Kamrul
Islam via Sandeep More)
> Allow native library auto included through java.library.path property
> ----------------------------------------------------------------------
>
> Key: KNOX-868
> URL: https://issues.apache.org/jira/browse/KNOX-868
> Project: Apache Knox
> Issue Type: Improvement
> Reporter: Mohammad Kamrul Islam
> Assignee: Mohammad Kamrul Islam
> Fix For: 0.12.0
>
> Attachments: KNOX-868.1.patch
>
>
> Currently user can add custom jars by copying it into $GATEWAY_HOME/ext
> directory. However, there is no easy way to include native library (.so).
> The use case is: a lot of authentication mechanism libraries are implemented
> using C/C++ library. And user may want to integrate it with Knox.
> One of the option could be: user can add .so files into
> $GATEWAY_HOME/ext/native directory. At the same time, gateway service can
> include that directory through java.library.path property during start up.
> We can potentially use launcher.cfg to support it.
> Any other alternative approach?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
