You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Mohammad Kamrul Islam (JIRA)" <ji...@apache.org> on 2017/02/16 19:41:41 UTC
[jira] [Updated] (KNOX-868) Allow native library auto included
through java.library.path property
[ https://issues.apache.org/jira/browse/KNOX-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mohammad Kamrul Islam updated KNOX-868:
---------------------------------------
Attachment: KNOX-868.1.patch
I took the simplest approach. It worked for me :)
Please review.
> 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
> 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)