[Mono-bugs] [Bug 652167] New: ASP:LoginView does not appear when it contains rolegroups with custom roles.

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=652167

https://bugzilla.novell.com/show_bug.cgi?id=652167#c0


           Summary: ASP:LoginView does not appear when it contains
                    rolegroups with custom roles.
    Classification: Mono
           Product: Mono: Runtime
           Version: 2.8.x
          Platform: 64bit
        OS/Version: Ubuntu
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: JIT
        AssignedTo: lupus at novell.com
        ReportedBy: dbenson at tunewiki.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


Created an attachment (id=399043)
 --> (http://bugzilla.novell.com/attachment.cgi?id=399043)
a basic website project which demonstrates the issue.

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12)
Gecko/20101026 Firefox/3.6.12

This is a website bug.

In mono, the asp:loginview control will not display content for roles added
through a custom handler in global.asax.cs. This works in asp.net. Have not
tested with roles created in any other way.

On application_authenticateRequest, I recreate the user with custom roles: 

HttpContext.Current.User = new GenericPrincipal(id, roles.Split(','));

This role shows correctly in Page.User.IsInRole(), but for some reason,
asp:loginview does not load the content for the specified role.


Reproducible: Always

Steps to Reproduce:
1.run the included sample website
2.login with a custom role
3.the loginview disappears.
Actual Results:  
the asp:loginview does not appear when logged in, even though the user is in a
role specified by a rolegroup

Expected Results:  
the loginview should show the rolegroup for the specific user's role

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.