cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CXF-5462) STSClient.validate operation does not parse TokenType or Lifetime elements in RSTR
Date Fri, 24 Mar 2017 12:51:41 GMT

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

Colm O hEigeartaigh reassigned CXF-5462:
----------------------------------------

    Assignee: Colm O hEigeartaigh

> STSClient.validate operation does not parse TokenType or Lifetime elements in RSTR
> ----------------------------------------------------------------------------------
>
>                 Key: CXF-5462
>                 URL: https://issues.apache.org/jira/browse/CXF-5462
>             Project: CXF
>          Issue Type: Bug
>          Components: STS
>    Affects Versions: 2.7.2
>         Environment: MacOSX 10.8.3. Tomcat 6.0.36.
>            Reporter: Dirk Hogan
>            Assignee: Colm O hEigeartaigh
>
> I am using the org.apache.cxf.ws.security.trust.STSClient class to consume the STS. The
SecurityToken instances returned as part of the Validate operation invoked with a TokenType
other than Status (i.e. token transformation) have null tokenType and created/expires values.

> Looking around line 1066 of the 2.7.2 STSClient or around line 120 of the trunk STSClient,
it looks like it would be pretty straightforward to parse out the TokenType and Lifetime elements
in the RSTR so that the tokenType and created/expiers fields in the returned SecurityToken
instances could be set.
> If folks decide that this is worth doing, I would be happy to submit a patch.  



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

Mime
View raw message