Permissions' Settings Tab - Wrong Display (Full Version)

All Forums >> [Web Development] >> Server Issues



Message

Wage Slave -> Permissions' Settings Tab - Wrong Display (6/12/2002 10:49:28)

Does anyone know why the Settings tab of the Permissions window in FP2000 would start defaulting to "Use same permissions as parent web" even though the active setting is actually "Use unique permissions for this web"?

My NT server on the office intranet is running FP2000 extensions release 1.2. Whenever I create a new subweb under the root, I set it as "Use unique permissions for this web". The administrator of a private site ("Only registered users have browse access") kept reporting that people she'd given Browse permission to were being denied access. I discovered that her session would always show the "parent web" setting as active. At the same time, I would open the site with my NT id (which belongs to the Administrators group on the server) and the setting would be "unique permissions". Her two fellow administrators reported the same "parent web" setting when they opened the site on their workstations. We're all using the FP2000 client.

I concluded that her site visitors' access woes were resulting from the "parent web" default being applied when she made a change under the Users tab. To determine the extent of the problem, I gave a colleague Administer permission for this site then logged onto the network under his NT id on my workstation and opened the site. It displayed as "parent web" as well. I went back in under my NT id, found three test sites that I knew absolutely were "unique permissions", gave my colleague Administer permission to the three then logged back into my workstation under his NT id. To my surprise, each of these sites came up with "parent web" checked even though the act of opening them proved that the "unique permissions" (still viewable in the Users tab) were active.

I had an administrator of three different sites on the same server check the settings on those and he reported that two were showing "unique permissions" yet the third showed "parent web".

Nothing like this has ever occurred before in the year-and-a-half that this server has been hosting sites under Release 1.2. Any ideas what's wrong and how to correct it?



Wage Slave -> RE: Permissions' Settings Tab - Wrong Display (6/18/2002 15:53:51)

There's more:

- A) When the site administrator (Administer permission) opens the site and goes into permissions:
  • the Settings tab shows "parent web"

  • functions on the other tabs are greyed out

  • the Users tab lists unique permissions, not those of the parent web


- B) When the server administrator (member of server's Administrators group) opens the root first then opens the subweb by double-clicking it in the Folder List, the Settings tab value is "unique".

- *** C) When the server administrator opens the subweb directly (by typing the subweb address in the "Folder name" box of the Open Web window), permissions show the same as they do for the site administrator: Settings = "parent web", other tab functions greyed out, unique permissions listed in Users tab.

- I re-applied the extensions to the sites in question but that had no effect. I created new subwebs but the results were the same. It didn't matter if, in the New Subweb Wizard, I chose "Use different administrator for this web" or chose "Use same administrator as parent web" then later flipped over to "unique permissions" in the Settings tab.

- *** The site administrator can change the Settings value from "parent web" to "unique permissions" then add in new Users. The changes stick. This also introduces some interesting wrinkles:
  • If the server administrator opens the site directly (method C), he's still in sync with the site administrator - the Settings value is "unique".

  • If the server administrator opens the site from the root (method B), he's still out-of-sync with the site administrator - Settings is "parent web".

  • When the site administrator flips the Settings value from "parent web" to "unique", the unique permissions under the Users tab are kept. When the server administrator does the same flip (whichever way - B or C - the subweb is opened), the unique Users permissions are wiped out.


In short, there seem to be two factors which determine how the permissions are going to be displayed:

1) Which method is used to open the site

2) Which method was used to open the site by whoever changed the permissions last.

Any suggestions?

Wage Slave




Wage Slave -> RE: Permissions' Settings Tab - Wrong Display (8/3/2003 10:28:03)

Found the explanation for this one, thanks to Microsoft Support. It' s due to FP2000' s difficulties with handling changes of text case in subweb names. Not a problem with FP2002.

If you' re running FP2000 against FP2000 server extensions like I am, you can reproduce this yourself. Go into Open Web and delete the Web Folder for the site you want to open. Open the site by entering its proper spelling (case-wise) in the Folder Name field. Go into Tools/Security/Permissions and verify the settings under the Settings and Users tabs. Close the site, go to Open Web again, delete the Web Folder again (if it' s been recreated), and enter the sitename in the Folder Name field again but with different letters capitalized or lower-cased. When you check the Settings and Users tabs again, you' ll see the differences I noted in my earlier postings.

When you initially open a new site in the FrontPage tool, you must use the same capitalization that' s been used for the subweb when it was created in IIS. Once a Web Folder has been set up locally with this correct address then you can use whatever capitalization you like when you type the name in the Folder Name box; it will default or map to the Web Folder. If the Web Folder has the incorrect capitalization, however, then you get the distorted permission settings.

The true permissions are those you see when you open the subweb via the root web listing or directly in the Folder Name box (when there' s no web folder) using the proper capitalization of the subweb. When an administrator uses a different-case spelling, he gets a corrupt view of the permissions. If he changes this view' s setting from " parent" to " unique" , he flips the true setting to " parent" and can use his false-unique view to slip unique permissions in with the parent settings for the subweb.



caywind -> RE: Permissions' Settings Tab - Wrong Display (8/4/2003 5:12:37)

yikes! hooray for Linux...case always matters



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.0625