Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi, We are looking for a solution for the following situation/goal; RBAC:Active-directory group membership (also nested one's) in two different domains (we got that sorted out via the "All_AD_Join_Points" group) are oure external identity sources tha...
Hi Arne,Thanks again for the extensive and detailed explanation, I really appreciate the way you are trying to think with me for a proper soloution.I finally (had a busy week) had a talk with our architect about changing the AD scheme and the way we ...
Hi Arne, Thanks again. This does look like a possible solution for our use case.We've (my colleague) found an article that describes the dynamic authorization profile a bit more in depth, similar to what you are proposing (we actually found this arti...
Hi Arne, Thanks again for helping me on this. The attributes are send correctly. So, indeed the authorization part works by itself. The problem we are facing is that we have several virtual instances on the device (ADOM/VDOM). And you can only push 1...
Hi Arne, Thanks for replying. I realize now that I have not shared enough information around our situation to clarify things. Sorry about that. Let me explain our case a bit further; FortiGate/FortiManager/FortiAnalyzer VDOM means Virtual DOMain. Thi...
