Discussion Locked

Site Server Personalization and Membersh

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have Site Server 3.0 installed (with SP2), using Membership Authentication on top of IIS 4.0. The Membership Directory is stored in a SQL 7.0 database. The IIS 4.0 web that is used for hosting web pages makes use of the HTML Forms Authentication.
When new members are created on the ou=Members container, the properties dialog box of the members container normally allows assignment of security strings (called ACL's) for controlling access to members (the same can be done on each member within the container also).

The problem is that whatever the permissions are added, after the dialog box is closed and open again, the permissions vanish! Its as though no permissions have been granted. In fact this happens at all levels (even in the Membership Server instance level). The downside of this is that, I'am not able to update any attribute values using the SetInfo() and GetInfo() methods (but these methods work fine, if the user involved is the Administrator).

Another problem is that, we as a team, are

10 replies

by gbworld

To understand how to program Site Server, the best books on the market are those by Wrox. In fact, while older, the Personalization and Membership book is wonderful.

Another good resource is to look at ADSI in the MSDN library (and a variety of books). While the containers in Site Server are a bit different in some respects, the technology is very similar.

As your post dropped off prior to finishing, I am not certain what your problems with the team are. Also, I am not sure if you are talking about items disappearing in the admin tools, or programatically. I am assuming in the tools, so I have offered the programatic direction for resolution.

Greg

by michael roark - ccna/da mcp 3csa

I believe if I understand the problem correctly, you want others besides the Administrator login to be able to change the ACLs?
Most ACLs can only be changed by the administrator in the first place, but there are other options for doing this with IIS5 I believe, have you upgraded yet?

This discussion is closed to new replies.