Is the <authentication/> section required in web.config for Umbraco to work?
Hi
I'm trying to integrate Servicestack.net webservices with Umbraco to serve data to smartphone App's, and basically it work - until I add authentication. Because Servicestack work with http commands, it returns an 401 if the App (in this case) needs to authenticate. But because the <authentication /> section is present in web.config, IIS takes over and redirects to loginUrl instead of feeding the 401 to the App. I can get to work if I remove the section, and Umbraco seems to work anyway, if you protect a page, because you specify the login page, from the "Protect" dialog in Umbraco backend.
The question is: Is this ok, to remove this section, or is there something that I didn't think of, that brakes some part of Umbraco?
Is the <authentication/> section required in web.config for Umbraco to work?
Hi
I'm trying to integrate Servicestack.net webservices with Umbraco to serve data to smartphone App's, and basically it work - until I add authentication. Because Servicestack work with http commands, it returns an 401 if the App (in this case) needs to authenticate. But because the <authentication /> section is present in web.config, IIS takes over and redirects to loginUrl instead of feeding the 401 to the App.
I can get to work if I remove the section, and Umbraco seems to work anyway, if you protect a page, because you specify the login page, from the "Protect" dialog in Umbraco backend.
The question is: Is this ok, to remove this section, or is there something that I didn't think of, that brakes some part of Umbraco?
Cheers Bo
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.