How To: Configure Nested Group Restriction on a Realm

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: All versions

     

    Overview

    This article explains how to configure a SecureAuth realm that has a group restriction enabled to also check nested Active Directory (AD) group membership, so that users in a nested group are included by the restriction, not just users in the top-level allowed group.

     

    Configure Nested Group Restriction

    1. On the realm's Data tab, under Profile Provider Settings, set Same As Above to False and Default Profile Provider to Directory Server.

    Profile Provider Settings panel with Same As Above set to False and Default Profile Provider set to Directory Server.

    1. Under Profile Connection Settings, configure the data store connection with the same settings used on your primary realm connection (the one containing user information). Set Advanced AD User Check to True if you want to check for blocked accounts and expired passwords. Make sure Include Nested Groups is checked, and leave Allowed User Groups blank.
    2. Under Profile Fields, make sure the Groups property's Field is set to MemberOf.

    Profile Connection Settings panel with Include Nested Groups checked, and Profile Fields panel with the Groups property's Field set to MemberOf.

     
     

    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.