Enterprise Policy URL Condition

From: Darren Mombourquette (dmombour_at_hotmail.com)
Date: 08/26/03 

Date: 26 Aug 2003 09:22:19 -0700

Hello,
I am trying to set an Enterprise policy based on a URL condition for
our WebServer and the policy does not seem to take effect on client
machines.
What I did was this:
On our domain I created two security policies in the Enterprise Level.
One a strong name condition based on our company public key. And
another a URL condition with the following setting
"http://ourwebserver/*" and I granted full trust to both and set the
level final attribute.
Now the strong named security policy works. When I try to run .net
apps that are strong named off of a network share the policy is
evaluated and the app runs successfully. But when I try to run an app
via a URL off of our webserver the code isn't trusted.

Can you not use a URL condition for an Enterprise Policy?

Thanks,
Darren Mombourquette

Relevant Pages

  • Re: Enterprise Policy URL Condition
    ... couple of embeded user controls, and a couple of client side apps that ... controls I believe have to do with using other policy types with ... would create an Enterprise policy URL condition for the same URL, ... saving them from running the utility on all client machines. ...
    (microsoft.public.dotnet.security)
  • Re: Enterprise Policy URL Condition
    ... > will be run directly off the server. ... > controls I believe have to do with using other policy types with ... > would create an Enterprise policy URL condition for the same URL, ...
    (microsoft.public.dotnet.security)
  • Enterprise Policy URL Condition
    ... to "http://ourwebserver/ \*" in the security file. ... >I am trying to set an Enterprise policy based on a URL ... >On our domain I created two security policies in the ... >Can you not use a URL condition for an Enterprise Policy? ...
    (microsoft.public.dotnet.security)
  • [fw-wiz] Security policy language
    ... However, there is something I'm still missing from what has been said: why are we thinking to a single, complete and comprehensive policy language rather than to more languages used to express the same policy by different people? ... I agree with all of you that the definition of a complete security policy language is almost impossible and probably useless. ... The consequence is that no functional constraint can be automatically produced from the enterprise statement for the low-level security policy and there is no way to automatically check whether the actual security configuration complies with the "personal use" defined by the enterprise policy. ...
    (Firewall-Wizards)
  • Re: Code Access Security
    ... modify the CAS enterprise policy so that code outside the "my computer" zone ... distributing the new policy via an MSI would probably be the best bet. ... Create a backup of your current enterprise policy level file ... Condition type: Zone ...
    (microsoft.public.dotnet.security)