This content has been marked as final. Show 2 replies
Studio 2.3 will instantiate a MDEXSecurityManager once per user session created, with the implementation class name read from the config property df.mdexSecurityManager.
If you need custom behaviour (such as that in your two MDEXSecurityManager implementations), you would need to create a third implementation which delegates to the correct implementation (or combine the classes into a single class if that is an option). Can you distinguish between which security manager instance/logic is required, based on the context provided in the applySecurity() call (PortletRequest, MDEXState, Query)?
That's what I am thinking about. I plan to configure each data source with its corresponding MDEXSecurityManager.