directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRKRB-654) Add support to receive a JWT AccessToken via the GSS API
Date Fri, 08 Sep 2017 10:27:02 GMT

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

Colm O hEigeartaigh commented on DIRKRB-654:
--------------------------------------------

Thanks [~drankye], switching to use the ExtendedGssContext in the tests does the job. 

> Add support to receive a JWT AccessToken via the GSS API
> --------------------------------------------------------
>
>                 Key: DIRKRB-654
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-654
>             Project: Directory Kerberos
>          Issue Type: Task
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.1.0
>
>         Attachments: DIRKRB-654.patch
>
>
> https://issues.apache.org/jira/browse/DIRKRB-651 added support to send a JWT Access Token
via the GSS API. This task is to add support to receive it. The AuthorizationDataEntry values
are converted to KrbTokens, which are in turn set as a public credential on the JAAS Subject.
> Question: Is this the correct place to store the received AuthorizationData entries?
I don't think it's right to store the JWT Tokens on the JAAS Subject of the receiver....



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

Mime
View raw message