Re: Enterprise Policy URL Condition
From: Darren Mombourquette (dmombour_at_hotmail.com)
Date: 08/27/03
- Next message: Keith Patrick: "Re: MD5CryptoServiceProvider.ComputeHash throws CryptographicException"
- Previous message: Charles Leonard: "ASPNET Event Log Access"
- In reply to: Matt L: "Enterprise Policy URL Condition"
- Next in thread: Marcelo Birnbach [MS]: "Re: Enterprise Policy URL Condition"
- Reply: Marcelo Birnbach [MS]: "Re: Enterprise Policy URL Condition"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 27 Aug 2003 08:25:09 -0700
Hi Matt,
I just checked my enterprise.config file and it looks fine. My URL
condition did not get escaped in the config file, it is written as
Url="http://serveraddress/*" which appears to be correct.
Because if I create a local "Machine policy" for any URL it works fine
using this notation and when checking the config file is does not get
escaped.
I looked at your previous post and you have written the notation to be
"http://serveraddress/.*" I don't believe the . before the * is the
correct notation.
Anyway I did try to escape my * and entered
Url="http://serveraddress/\*" in my config file and it still did not
work with clients of the domain.
Darren
"Matt L" <matt@nospam.com> wrote in message news:<020401c36bf4$5f9a0ef0$a301280a@phx.gbl>...
> I just posted a similar question, and the problem is that
> the statement "http://ourwebserver/*" becomes escaped
> to "http://ourwebserver/\*" in the security file. In
> otherwords, the '*' becomes a literal and the only URL
> that matches is literallyl "http://ourwebserver/*", which
> is nothing. The only workaround I have found so far is to
> hand edit the security.config file to
> change "http://ourwebserver/\*"
> to "http://ourwebserver/*". Be warned that any additional
> modifications to the permission set using the
> configuration MMC snap-in will cause your hand changes to
> be lost.
>
> Matt
>
> >-----Original Message-----
> >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
> >.
> >
- Next message: Keith Patrick: "Re: MD5CryptoServiceProvider.ComputeHash throws CryptographicException"
- Previous message: Charles Leonard: "ASPNET Event Log Access"
- In reply to: Matt L: "Enterprise Policy URL Condition"
- Next in thread: Marcelo Birnbach [MS]: "Re: Enterprise Policy URL Condition"
- Reply: Marcelo Birnbach [MS]: "Re: Enterprise Policy URL Condition"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
