After closer inspection it seems like I am logging my user without a problem however I cannot see the the content tree for my site, you can see what happens here: http://yfrog.com/h3ate9p
I can however see all the other areas, such as the Users, Templates etc. I can even right click on the top Content node and add a new item (which I can then see has been created if I revert my code back to the origninal).
Does anyone have any idea what might be happening here? Nothing obvious is being written to the logs.
The sign on functionaility instructions that I was using wanted the web.config to change the authentication mode from:
<authentication mode="Forms">
to
<authentication mode="None">
This allowed me to login but sent the treebuilder for the menus into a bit of a panic. I changed it back and it works fine. Not something most people would ever run into but it's worth knowing I suppose...
Custom Backoffice logging in
Hi all,
I'm trying to swap out the standard backoffice login for umbraco for a single sign on solution (see http://our.umbraco.org/forum/developers/api-questions/21065-Logging-in-a-Backend-Umbraco-User-via-API to see the gist over what I'm attempting) and am having a bit of a nightmare!
After closer inspection it seems like I am logging my user without a problem however I cannot see the the content tree for my site, you can see what happens here: http://yfrog.com/h3ate9p
I can however see all the other areas, such as the Users, Templates etc. I can even right click on the top Content node and add a new item (which I can then see has been created if I revert my code back to the origninal).
Does anyone have any idea what might be happening here? Nothing obvious is being written to the logs.
Many Thanks,
Steve
Ok, the solution was a little frustring...
The sign on functionaility instructions that I was using wanted the web.config to change the authentication mode from:
<authentication mode="Forms">
to
<authentication mode="None">
This allowed me to login but sent the treebuilder for the menus into a bit of a panic. I changed it back and it works fine. Not something most people would ever run into but it's worth knowing I suppose...
is working on a reply...