Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 1 subscriber
  • Views 2581 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Backend Group membership based on Container

addrockk
I'm switching from eDir SSO to AD SSO, and I'm having some difficulty with group processing. In eDir, I could make a group with backend membership, and point it at an eDir Organization Unit, and everything worked. 
If I try to do that in AD, it simply doesn't work. It only works when I point it at a group object. Do I really have to maintain a separate group for every OU, or is there a way to get it to recognize OU's for backend membership groups when using AD?

TIA,
Adam


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to BAlfson
    Correct, so your Fallback for the AD-SSO Profile can be the Default Block Action.

    Cheers - Bob


    OK one last question about this:
    What's the difference between "Default Filter Action" and "Default content filter block action"?