[
https://issues.apache.org/jira/browse/KNOX-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853379#comment-15853379
]
Larry McCay commented on KNOX-852:
----------------------------------
Taken care of in KNOX-850
Commit 47c1f4ac2ec942cad7472f7aa3ef6201b96f1e0b in knox's branch
refs/heads/master from Larry McCay
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=47c1f4a ]
KNOX-850 - KnoxToken API for Acquiring a Knox Access Token
> Knox CLI Command for Knox Login
> -------------------------------
>
> Key: KNOX-852
> URL: https://issues.apache.org/jira/browse/KNOX-852
> Project: Apache Knox
> Issue Type: Sub-task
> Components: KnoxCLI
> Reporter: Larry McCay
> Assignee: Larry McCay
> Labels: kip-4
> Fix For: 0.12.0
>
>
> Similar to a kerberos kinit, we need a CLI command to authenticate to a
> KnoxToken service and request a token for an SSO session across API
> interactions.
> The CLI should include parameters for cluster/topology-name and potentially a
> list of services required. A combination of KnoxToken service config and
> these parameters will determine: 1. whether the token can be acquired and 2.
> the audience claims added to the token for access decisions when accessing
> services using it as a bearer token.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
