[jira] [Commented] (KNOX-742) Export Commands in KnoxCLI for the gateway-identity Public Cert

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KNOX-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432735#comment-15432735 ] 

ASF subversion and git services commented on KNOX-742:
------------------------------------------------------

Commit e5ef45aaecd5dc7372403302fb8be21e485f3a45 in knox's branch refs/heads/master from [~lmccay]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=e5ef45a ]

KNOX-742 - Export Commands in KnoxCLI for the gateway-identity Public Cert

> Export Commands in KnoxCLI for the gateway-identity Public Cert
> ---------------------------------------------------------------
>
>                 Key: KNOX-742
>                 URL: https://issues.apache.org/jira/browse/KNOX-742
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: KnoxCLI
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>             Fix For: 0.10.0
>
>         Attachments: KNOX-742-001.patch
>
>
> In order for the knox admin to be able to provide a PEM or JKS file with the gateway's public cert, we currently need the admin to use keytool or some other tooling for exporting it.
> Keytool isn't always available in deployment environments.
> This patch will add an export command to the KnoxCLI that can export the public cert to a PEM encoded file or create a JKS type keystore that can then be used as a client truststore where appropriate.
> Something like:
> bq. knoxcli.sh export-cert [--type (PEM|JKS)]
> Where the optional type argument defaults to PEM.
> The exported files will be stored in the {GATEWAY_HOME}/data/security/keystores directory as:
> gateway-identity.pem and gateway-client-trust.jks respectively.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)