Re: 401 Unauthorized; the sequel
Security is by project, not database, and each project has its own security and its own GUID value. Therefore, you can have multiple projects from the same source database publishing to the same server as long as each project publishes to a different target folder. Each will have its own unique security environment. What won't work is publishing from the same project to 2 locations on the same server. In that case, only the first instance opened will work. What will also not work is publishing 2 projects to the same folder on the server. In that case, the security applied is the last security published.
All security is tied to the folder under the webroot defined as the application root for that project. Security settings are initially loaded when the first page request tied to that application root is called. The security loads with the GUID from that folder and saves the folder location. When the next page request comes in, it uses the security GUID value from the new page's application root to check the appropriate security settings. Part of that security check is a verification that the current root folder matches the original application root for that GUID. If they don't match, you will get the 403 message.
Security is by project, not database, and each project has its own security and its own GUID value. Therefore, you can have multiple projects from the same source database publishing to the same server as long as each project publishes to a different target folder. Each will have its own unique security environment. What won't work is publishing from the same project to 2 locations on the same server. In that case, only the first instance opened will work. What will also not work is publishing 2 projects to the same folder on the server. In that case, the security applied is the last security published.
All security is tied to the folder under the webroot defined as the application root for that project. Security settings are initially loaded when the first page request tied to that application root is called. The security loads with the GUID from that folder and saves the folder location. When the next page request comes in, it uses the security GUID value from the new page's application root to check the appropriate security settings. Part of that security check is a verification that the current root folder matches the original application root for that GUID. If they don't match, you will get the 403 message.
Comment