Bug 1170791 - [GSS] (6.3.z) SAML11TokenProvider and SAML20TokenProvider do not take CLOCK_SKEW into account (PLINK-639)
Summary: [GSS] (6.3.z) SAML11TokenProvider and SAML20TokenProvider do not take CLOCK_S...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: PicketLink
Version: 6.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.3.3
Assignee: Boleslaw Dawidowicz
QA Contact: Pavel Slavicek
URL:
Whiteboard:
Depends On: 1170792 1188642
Blocks: eap633-payload 1167409 1176536
TreeView+ depends on / blocked
 
Reported: 2014-12-04 21:31 UTC by Derek Horton
Modified: 2019-08-19 12:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1167409
: 1170792 (view as bug list)
Environment:
Last Closed: 2019-08-19 12:40:26 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker PLINK-636 0 Major Resolved The SAML11TokenProvider and SAML20TokenProvider do not take the CLOCK_SKEW setting into account during processing 2016-10-26 11:08:35 UTC

Description Derek Horton 2014-12-04 21:31:57 UTC 
Description of problem:
SAML11TokenProvider and SAML20TokenProvider do not take CLOCK_SKEW into account (PLINK-639)
Comment 5 JBoss JIRA Server 2014-12-18 11:37:34 UTC 
Pedro Igor <pigor.craveiro> updated the status of jira PLINK-636 to Resolved
Comment 8 Dominik Pospisil 2015-01-08 09:43:32 UTC 
Fix included in 2.5.3.SP14-redhat-1.
Comment 9 Ondrej Lukas 2015-01-20 14:30:14 UTC 
Verified in EAP 6.3.3.CR1.
Note You need to log in before you can comment on or make changes to this bug.