Target Audience not working for LDAPCP groups added to sharepoint groups

[WEIGLBRC-Taylor]

I initially put in this issue re: targeted navigation and LDAPCP groups. I found that if I added LDAPCP users to a sharepoint group, and assigned the sharepoint group as a target audience for the navigation (structured current or structured global) the end result was success! I assumed the same would be true re: adding LDAPCP groups to a sharepoint group.

Unfortunately, I tested this out yesterday and when I added an LDAPCP group that my AD user is a member of to a sharepoint group that was the target audience of a navigation item, I was still not able to see the navigation item.

I'm hoping you can provide me with some insight or troubleshooting suggestions, as I'm not really sure how to move forward...

TIA!

Taylor

[Yvand]

@WEIGLBRC-Taylor it's been a very long time since I used audiences so I need a refresh: Can you confirm you create an audience in the User Profiles service, define rules, compile this audience, and then you can use this audience in the navigation ? If the above is correct, you can view the membership of the audience. What do you see here?

[WEIGLBRC-Taylor]

That is one type of an audience, a compiled audience. Apologies for not being more specific. The type of audience I am using is the audience for Navigation items. I have attached a screenshot.

the group "All_Access" is a sharepoint group. When I put an LDAPCP "role" group into the "All_Access" group, members of the LDAPCP "role" group don't see the navigation element. However, If I manually add the LDAPCP users that are in the LDAPCP "role" group into the "All_Access" sharepoint group, the users see the navigation element.

[Yvand]

@WEIGLBRC-Taylor sorry for the late reply. I'm not sure how this particular configuration is supposed to work. Did you enable the augmentation in LDAPCP configuration?

[WEIGLBRC-Taylor]

I did. I’m guessing this is another “special sharepoint thing” ☹

[Yvand]

It could be a limitation, yes. In any case, I really don't see anything to do in LDAPCP side to fix this, sorry...

[github-actions[bot]]

Stale issue message