Hello Rick, I don't believe that there is a way to set this up the way you are looking for on the rootPOA. The normal way to do this is through the creation of new POAs, which I believe is what you describe as happening in most instances. I believe that rootPOAs are supposed to be created with a standard set of default policies and should not be changeable.
As for the accessing the ORB instance, I'll have to have a look at the IOR interceptor hierarchy. I not sure what is available at this point and I need to have a look at the interfaces to refresh my memory on this one. Darren On 4/6/07, Rick McGuire <[EMAIL PROTECTED]> wrote:
Geronimo has a security setup where it defines a security policy on the different POA instances it creates, and the IORInterceptor we install on the ORB checks for the effective policy and annotates the IOR accordingly. This works fine, but there are some situations where the rootPOA is used to activate and object, and since the rootPOA doesn't have the proper policy set, we end up generating incorrect IORs because the transport level security profiles are not getting set correctly. Is there a way to these policies on the rootPOA? Or failing that, is there a way to access the ORB instance inside the IORInterceptor context so I can query policy overrides that have been set on the ORB policy manager? Rick
