Bug: Profile Service Account Reverts to the Membership Value on a Split Profile Realm

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: 24.04
    Bug Number: Not provided in source
    Bug Status: Closed - Fixed
    Fixed in Version(s): 24.4.3 RU

     

    Overview

    On IdP 24.04 (vanilla), when a realm's Data tab uses a split profile setup — see How To: Configure a Split Profile Provider for the general setup procedure — updating the service account in the Profile section and clicking Save causes the field to revert back to the value currently set in the Membership section, instead of keeping the new value you entered.

     

    Cause

    This is a defect in the product: saving the Data tab does not persist a Profile section service account that differs from the Membership section's service account.

     

    Resolution / Workaround

    Upgrade to 24.4.3 RU or later, which resolves this defect.

    If you cannot upgrade immediately, manually edit the Profile section's service account value directly in the realm's web.config instead of through the Data tab.

     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.