You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Sandeep More (JIRA)" <ji...@apache.org> on 2017/08/24 15:30:00 UTC

[jira] [Updated] (KNOX-1002) Knox Token Service Client data with comma separated list of values for a key should be handled

     [ https://issues.apache.org/jira/browse/KNOX-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandeep More updated KNOX-1002:
-------------------------------
    Fix Version/s: 0.14.0

> Knox Token Service Client data with comma separated list of values for a key should be handled
> ----------------------------------------------------------------------------------------------
>
>                 Key: KNOX-1002
>                 URL: https://issues.apache.org/jira/browse/KNOX-1002
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>            Reporter: J.Andreina
>             Fix For: 0.14.0
>
>
> If in case in client data , a key has got list of comma separated values, then only the first value in the list is considered in the response.
> Should be able to  differentiate between commas within values and comma used as delimiter for key value pair. When used escape character for comma within values list is also not working.
>  
> For example
> Configured a comma separated list of value for a key as below
> {code}
>             <name>knox.token.client.data</name>
>             <value>key1=value1,value2,value3,key2=value4</value>
>  {code}
> *Response is as follows:*
> {"access_token":"eyJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJndWVzdCIsImF1ZCI6InRva2VuYmFzZWQiLCJpc3MiOiJLTk9YU1NPIiwiZXhwIjo1MTUwMzU1MTA1Mn0.bpGoIsVTp2sgF74kyQYRRNAW9wW-nhg5_A3N40Zfb1FuK5apED-PDNfZBroMQ9wLy80egPWMqPbTVFa9vrdZ2RJgNdOfnlaE-Ey-qr7khRZQAaeb42aGUjGxnUAipZvoRbp48lWH-w3wOTq5qV6EBu0cczxqw0rxD2zZTmsk2oQ",{color:red}"key1":"value1","key2":"value4"{color},"target_url":"https://$KNOX_HOST:$KNOX_PORT/gateway/tokenbased","token_type":"Bearer ","expires_in":51503551052130}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)