Bug ID 631745: SSO Credential Mapping does not take effect on the primary-auth domain of Multidomain SSO

Last Modified: May 01, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4

Opened: Dec 05, 2016
Severity: 3-Major

Symptoms

SSO Credential Mapping (serverside SSO) does not take effect when accessing a resource through the primary-auth domain of Multidomain SSO (clientside SSO)

Impact

End users are unable to authenticate through SSO Credential Mapping to resources on the primary-auth domain.

Conditions

-- Multidomain SSO configured in the access profile (clientside SSO). There is a resource protected on the primary-auth domain. -- SSO Credential Mapping agent (serverside SSO) configured in the access policy.

Workaround

There is no workaround at this time.

Fix Information

None

Behavior Change