Bug ID 596336: SSO object is not assigned to Access Profile on usage of Wizard

Last Modified: Nov 07, 2022

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, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
13.0.0

Opened: May 28, 2016
Severity: 3-Major
Related Article:
K72210155

Symptoms

With successful creation of APM-specific objects using Wizard, assigning an SSO object to a profile does not add the SSO object to the access profile.

Impact

Misleading, because the chosen SSO object is not associated with the profile. You must manually assign the SSO object to the profile after completing the wizard.

Conditions

Wizard should complete all the user steps, and create all required objects along with associations.

Workaround

Assign the SSO to Access Profile on Profile profile properties :: SSO :: Auth Domains tab on UI or using TMSH.

Fix Information

The system now auto-create the association between Profile and SSO Object with successful creation of APM-specific objects using Wizard.

Behavior Change