I have built some custom authentication library but have run into a problem.
The custom code uses MySql.Data.dll(a library from MySQL for .NET) to
authenticate users against a MySQL db.
I get an connection error when I attempt to connect and believe that it is
because of CodeGroup permissions that need to be set in the
rssrvpolicy.config file.
I have added a code group as:
<CodeGroup
class="UnionCodeGroup"
version="1"
Name="MySQL"
Description="Code group for the security extension MySQL"
PermissionSetName="FullTrust">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="D:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\bin\MySql.Data.dll"
/>
but still no sucess.
Any ideas? Are there any other security settings?
The server is 2003 with IIS 6.
ThanksI used filemon.exe from SysInternals.com to debug a security
permissions problem with my custom assembly recently. It will show you
if the dll is being loaded and if not, what is preventing it from being
loaded. My solution involved using the file properties - security tab
to compare the allowable user groups on the custom dll to other dll's
in the bin folder.
This may be an obvious question... you have given permission to the
MySQL.Data.dll, but have you given the correct permissions to your
custom dll that uses that library?
I have also seen other posts that comment on the placement of the code
group in the code group heirarchy. Most recommend placing new code
groups right under the root code group node. Let us know what you find.|||Thank so much for your thoughts.
I took your advice and changed the order of the code groups for the DLL's
and it worked. I have the MySQL dll entry followed by custom library.
What is also to be noted is that I did not have to add any entries for the
MySQL dll or my custom dll when I was working on 2000 server with IIS 5.0.
IIS 6.0 has much tighter security.
Problem solved.
Thanks again,
Kevin
<bcsmith@.gmail.com> wrote in message
news:1106250549.705855.130230@.c13g2000cwb.googlegroups.com...
>I used filemon.exe from SysInternals.com to debug a security
> permissions problem with my custom assembly recently. It will show you
> if the dll is being loaded and if not, what is preventing it from being
> loaded. My solution involved using the file properties - security tab
> to compare the allowable user groups on the custom dll to other dll's
> in the bin folder.
> This may be an obvious question... you have given permission to the
> MySQL.Data.dll, but have you given the correct permissions to your
> custom dll that uses that library?
> I have also seen other posts that comment on the placement of the code
> group in the code group heirarchy. Most recommend placing new code
> groups right under the root code group node. Let us know what you find.
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment