J
Jules
For a project I'm developing a custom ASP.NET 2.0 website.
The case:
- Forms authentication
- Cookieless forms authentication and sessionstates is enabled via
cookieless="AutoDetect".
- On the MasterPage a TreeView-menu is linked to the Web.sitemap.
The issue:
When I browse this website with a browser that allows cookies,
everything works ok. That is; I can sign in, and via the TreeView-menu
I can navigate through the website. Now when I browse this website with
a browser that doesn't allow cookies I can still sign in. However, when
I try to navigate through the website using the TreeView-menu, I get
signed out and prompted with the login page. To be sure it was the
TreeView-menu control that was responsible for this result, I added
some <asp:HyperLink>-controls which I used to navigate through the
site. This didn't give this issue.
Is there a known problem with the SiteMap navigation-controls in
ASP.NET 2.0 in combination with cookieless authentication? If so, are
there solutions of workarounds?
Help would be greatly appreciated! Actually the sooner the better, this
has hold us up for too long already.
The case:
- Forms authentication
- Cookieless forms authentication and sessionstates is enabled via
cookieless="AutoDetect".
- On the MasterPage a TreeView-menu is linked to the Web.sitemap.
The issue:
When I browse this website with a browser that allows cookies,
everything works ok. That is; I can sign in, and via the TreeView-menu
I can navigate through the website. Now when I browse this website with
a browser that doesn't allow cookies I can still sign in. However, when
I try to navigate through the website using the TreeView-menu, I get
signed out and prompted with the login page. To be sure it was the
TreeView-menu control that was responsible for this result, I added
some <asp:HyperLink>-controls which I used to navigate through the
site. This didn't give this issue.
Is there a known problem with the SiteMap navigation-controls in
ASP.NET 2.0 in combination with cookieless authentication? If so, are
there solutions of workarounds?
Help would be greatly appreciated! Actually the sooner the better, this
has hold us up for too long already.