Mojo interface implementations that rely on the security principal (origin, storage partition etc.) should use a BinderRegistry parametrized with that information rather than the current ad-hoc approach of currying-in either the RenderFrameHost or information obtained from the RenderFrameHost.
This bug tracks figuring out which sets of parameters to provide and to introduce BinderRegistryWithArgs<> for each set. Some possibilities:
BinderRegistryWithArgs<RenderFrameHost*>
BinderRegistryWithArgs<const url::Origin&, StoragePartition*, BrowserContext*, ...>
See also issue 734722 for plans for adding an isolation principal.
Comment 1 by slangley@chromium.org
, Oct 18 2017