Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.0.2.CR1, 7.0.2.GA
Affects Version/s: None
Component/s: Security
Labels:
None

Bugzilla References:
https://bugzilla.redhat.com/show_bug.cgi?id=1323281, https://bugzilla.redhat.com/show_bug.cgi?id=1337847
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.0.z.GA
Git Pull Request:
https://github.com/jbossas/redhat-picketlink-bindings/pull/16, https://github.com/jbossas/redhat-picketlink-bindings/pull/19, https://github.com/jbossas/redhat-picketlink-bindings/pull/21

Sprint:
EAP 7.0.2

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

SAML2STSLoginModule does not allow for configuring the ClockSkew

This can lead to authentication issues if the STS service and the STS client do not have synchronized clocks.

This fix needs to be included in eap 7.

clones

JBEAP-5359 (7.1.0) SAML2STSLoginModule does not allow for configuring the ClockSkew

Verified

incorporates

PLINK-735 SAML2STSLoginModule does not allow for configuring the ClockSkew

Open

PLINK-742 Misleading error message in the log about expired assertion in case of clock skew

Open

is incorporated by

JBEAP-4889 (7.0.2) Upgrade picketlink 2.5.5.SP2 to 2.5.5.SP3

Verified

is related to

JBEAP-5274 (7.0.z) Upgrade PicketLink Bindings to 2.5.5.SP3

Verified

Assignee:: Ivo Studensky

Reporter:: Derek Horton

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: 2016/04/01 2:44 PM

Updated:: 2021/10/24 6:19 AM

Resolved:: 2016/08/01 7:54 AM