You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/04/14 03:57:41 UTC

[jira] [Commented] (KNOX-923) Add ClientData to KnoxToken Service to Include in JSON Response

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

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

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

KNOX-923 - Add ClientData to KnoxToken Service to Include in JSON Response


> Add ClientData to KnoxToken Service to Include in JSON Response
> ---------------------------------------------------------------
>
>                 Key: KNOX-923
>                 URL: https://issues.apache.org/jira/browse/KNOX-923
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>             Fix For: 0.13.0
>
>
> There are times when a particular client may need to have additional data about the server instance/s where a KnoxToken can be used. For instance, it would be helpful to give a clue as to what cookie name may be expected by the KnoxSSO service. 
> After acquiring a token, a client may wrap the token in a cookie to be used by KnoxSSO compatible services/UIs.
> I envision a single param with a comma separated list of KV pairs that would then be added as single elements to the JSON response and interrogated by the client before use of the token.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)