Two endpoints, same entityID, different attribute filter?

[Cantor, Scott]

> It's the populations themselves that matter, not the attributes.  Maybe
> there's a better way to do it, but normally we control access to a
> service by a <PolicyRequirementRule> with a group entitlement.

I think you're trying to own a responsibility that ultimately is up to the service. I don't think it's a good idea to control access to something else based on whether other data gets released or not, but I also know that the person who set all that up doesn't agree.

Nevertheless, one entityID, one policy. The whole system is fundamentally designed around that assumption. But as I said, *can* you do it? Sure, you can do close to anything given Java or scripting. The response endpoint is in the outbound message context in a location I couldn't tell you offhand without reading the code, and the outbound message context is accessible from the ProfileRequestContext.
 
-- Scott