custom role provider not working on IIS but work fine in VS development server

Question

After deep googling I'm not found any solution or ways to troubleshoot my problem, so ask here. In first part of web.config

......
   <location path="DevReg.aspx">
    <system.web>
      <authorization>
        <allow roles="C,csvImportExport"/>
        <deny users="*,?"/>
      </authorization>
    </system.web>
  </location>
.......
  <system.web>
    <roleManager enabled="true" defaultProvider="MyRoleProvider">
      <providers>
        <clear />
        <add name="MyRoleProvider" type="DataAccess.Common.MyRoleProvider, DataAccess" applicationName="myapp" />
      </providers>
    </roleManager>
  </system.web>
.......

Main WebApp in other project in the same solution. When I run app in Visual Studio provider run fine -- authorization work as must, I also can call my provider from code (e.g IsUserInRole return right result). But after deployment to local IIS (Win 7/ IIS 7.5). I tried with VirtualDirectory and with WebApp with no luck.

When my app run in IIS look like server never use Role provider, only call Initialize method on start and newer more.

Please give me right direction to troubleshoot this problem, if need I will show more details.

are you using a different database when on IIS vs local host? — peroija, May 18 '12 at 16:55
@KrishanuDey application pool is default, I make only one change its allow 32 bit app to run because my host 64 bit — sage444, May 18 '12 at 18:52
@peroija is the same base on same host, and connection string never change — sage444, May 18 '12 at 18:54
@sage444 how did you solve this issue? i have no clue why IIS is ignoring my custom Role Provider — DJ., Jul 30 '14 at 17:13
@Djavier89 this is very old question, and I can't remember details so please check my answer below is all that I can give you as help — sage444, Jul 30 '14 at 17:50

score 0 · Answer 1 · answered May 18 '12 at 19:18

0

create a new Application Pool with Managed Pipeline Mode set to Integrated. Set the Identity value to NetworkService. After this set the newly created Application Pool as Application Pool of the site.

answered May 18 '12 at 19:18

Krishanu Dey

6,326
7
51
69

Thanks you for reply, this changed nothing but can you provide some explanation about your suggestion, this may get me some point to research – sage444 May 21 '12 at 12:20

score 0 · Answer 2 · answered May 22 '12 at 12:39

0

After changing point of view I found the problem. In project we also using one ugly HttpHandler with a row: Context.SkipAuthorization = true; that make all my troubles.

answered May 22 '12 at 12:39

sage444

5,661
4
33
60

custom role provider not working on IIS but work fine in VS development server

2 Answers2