SharePoint - Secure Field

NEW POST: Secure Field Installation stops

SiEBEN — Tue, 03 Nov 2009 14:09:06 GMT

Hello everyone

We have Sharepoint Services 3.0 x64 installed on an Server 2008 x64.
Single server installation with SQL server 2005 databases.
I am trying to install secure field but during system check I get a red X
"The Windows Sharepoint Services Administration Service is NOT started"

NEW POST: People picker - Allow AD (Feature Request)

steven_k — Mon, 19 Oct 2009 19:12:40 GMT

I have modified the SelectionSet="User,SPGroup" in SecureFieldEditor.ascx but im getting "Specified argument was out of the range of valid values." after Deploying the new solution. I am however able to select AD users now. I don't see where the people picker is specifying a range.

NEW POST: Want to use this Solution for URL field

NaveenKrJangir — Mon, 07 Sep 2009 11:47:41 GMT

HI, I want to use this solution for a URL type field, please suggest how to proceed further?

Also you are using a Looklist to store the data, but in my case i dont want to store data in lookup list.
Is it possible that i can apply the rendering logic in the same list?

Thanks in advance.

NEW POST: Creating Programmatically Using AddFieldAsXml

Adam_Ormond — Mon, 13 Jul 2009 15:25:49 GMT

I did some testing, and it would appear SPContext.Current is null when executed in this fashion. Any suggestions for how to address this problem? SPContext.Current is used numerous places throughout the source code.

I replaced SPContext.Current by using this.ParentList, but I'm now getting "Cannot change the lookup list of the lookup field". Ideas?

NEW POST: Creating Programmatically Using AddFieldAsXml

Adam_Ormond — Mon, 13 Jul 2009 14:57:26 GMT

I'm receiving an "Object reference not set to an instance of an object" from within EnsureSecureFieldStorageListExists, after calling AddFieldAsXml. It would appear the backend storage list isn't being created, but I'm not sure how to debug this project to determine what's causing the problem. Any suggestions would be greatly appreciated!

NEW POST: Bug Report - Error when editing the secure field in a customized list edit form

AngelaDeng — Wed, 01 Jul 2009 14:17:50 GMT

Hi,

I installed the VS2005 version of the setup package on WSS 3.0 web site. It works well with normal list. But I have problem to "edit" the secure field if it is on a customized edit form.

Here is the scenario:

I have a SP list based on a content type. I modified DispForm.aspx, EditForm.aspx and NewForm.aspx using SP Designer (by deleting the ListFormWebPart, and inserting a custome list form control). Then I added the secure field to the list and edit all three forms in order to "see" the newly added field. Everthing works great - I can create a new list item with the secure field filled, I can view secure field as I have permission to access the field. But when I tried to edit any item, it worked the first time. On the second time, when the secure field has value, I always got a warning message (see attached below), even though it saved it. I have tried to add the secure field using different ways: created it as a site column and added it to the underneath content type; directly added to the list. No luck, I always had the message on editing a "filled" secure field. (BTW, I'm the site administrator, I don't think it is security related)

Could anyone shed a light on this? Thanks so much!

Angela
----------------------------------------------------------------------------------------------------------------------------------------------
DataFormWebPartException: Data Source Conflict: Your changes conflict with those made concurrently by another user. Refresh the form and submit your changes again.
Microsoft.SharePoint.WebPartPages.DataFormWebPart.UpdateCallback(Int32 affectedRecords, Exception ex) +220
System.Web.UI.DataSourceView.Update(IDictionary keys, IDictionary values, IDictionary oldValues, DataSourceViewOperationCallback callback) +83
Microsoft.SharePoint.WebPartPages.DataFormWebPart.FlatCommit() +455
Microsoft.SharePoint.WebPartPages.DataFormWebPart.PerformCommit() +63
Microsoft.SharePoint.WebPartPages.DataFormWebPart.HandleOnSave(Object sender, EventArgs e) +43
Microsoft.SharePoint.WebControls.SaveButton.OnBubbleEvent(Object source, EventArgs e) +1390
System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +37
System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +118
System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +166
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +175
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1565

NEW POST: People picker - Allow AD (Feature Request)

Irish1115 — Wed, 29 Apr 2009 19:28:26 GMT

Had the same issue. Have it looking at AD users and groups after updating SelectionSet property from SelectionSet="SPGroup" to SelectionSet="User,SecGroup" for sharepoint:PeopleEditor in SecureFieldEditor.ascx

NEW POST: General Questions

mdressel — Wed, 04 Mar 2009 04:58:25 GMT

JoeH, When did it give you the Access Denied? Was it when you attempted to create the column?

JoeH wrote:
Hi. I'm using Sharepoint MOSS with Active Directory. I've gotten it to work, but had a few difficulties as well.

I added a Secure Column (I had to add users from the Sharepoint groups, as it didn't load the AD users), and it gave me an "Access Denied" error... even though I'm in the owners group of the site, and my user is listed explicitely as well as having "full control" fo the site.

However, then when I went back to the list, it had created the column.

If I try to modify permissions on the column, it also gives me the same error, and doesn't seem to save the changes this time.

At times when I have selected "New" to create a new item (it's a "Links" list), I've gotten the infamous "An unexpected error has occurred" screen. However, that is not occuring now, and I'm not sure what's changed (I think when I got that error I had multiple Secure Columns in the list).

When I get it to work, however, the data is correctly shown and hidden depending on the user I put.

NEW POST: General Questions

mdressel — Wed, 04 Mar 2009 04:57:55 GMT

Shabari, Can you provide any more information about what steps you are using when you get this error?

Shabari wrote:
Hello,

I have successfully deployed but when i try to use this, i am getting the following exception

The given key was not present in the dictionary. at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Microsoft.SharePoint.SPFieldCollection.CreateSPField(Int32 index)
at Microsoft.SharePoint.SPFieldCollection.EnsureSPField(Int32 index)
at Microsoft.SharePoint.SPFieldCollection.get_Item(Int32 iIndex)
at Microsoft.SharePoint.ApplicationPages.FieldCustomizationPage.OnPreRender(EventArgs e)
at Microsoft.SharePoint.ApplicationPages.FieldNewPage.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Can anybody help ?

thanks in advance..

NEW POST: People picker - Allow AD (Feature Request)

mdressel — Wed, 04 Mar 2009 04:49:09 GMT

The intention was not to limit who could be selected so I will take a look into this soon and let you know what I find.

NEW POST: General Questions

JoeH — Sat, 31 Jan 2009 15:27:38 GMT

Hi. I'm using Sharepoint MOSS with Active Directory. I've gotten it to work, but had a few difficulties as well.

I added a Secure Column (I had to add users from the Sharepoint groups, as it didn't load the AD users), and it gave me an "Access Denied" error... even though I'm in the owners group of the site, and my user is listed explicitely as well as having "full control" fo the site.

However, then when I went back to the list, it had created the column.

If I try to modify permissions on the column, it also gives me the same error, and doesn't seem to save the changes this time.

At times when I have selected "New" to create a new item (it's a "Links" list), I've gotten the infamous "An unexpected error has occurred" screen. However, that is not occuring now, and I'm not sure what's changed (I think when I got that error I had multiple Secure Columns in the list).

When I get it to work, however, the data is correctly shown and hidden depending on the user I put.

NEW POST: People picker - Allow AD (Feature Request)

JoeH — Sat, 31 Jan 2009 15:02:20 GMT

Hello. Great product and design. I installed it today, and it seems to work well. I would just ask for the feature to allow the people picker to read from Active Directory. As it is it only reads from Sharepoint groups it seems.
Thanks.

NEW POST: General Questions

Shabari — Sat, 31 Jan 2009 11:05:40 GMT

Hello,

I have successfully deployed but when i try to use this, i am getting the following exception

The given key was not present in the dictionary. at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Microsoft.SharePoint.SPFieldCollection.CreateSPField(Int32 index)
at Microsoft.SharePoint.SPFieldCollection.EnsureSPField(Int32 index)
at Microsoft.SharePoint.SPFieldCollection.get_Item(Int32 iIndex)
at Microsoft.SharePoint.ApplicationPages.FieldCustomizationPage.OnPreRender(EventArgs e)
at Microsoft.SharePoint.ApplicationPages.FieldNewPage.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Can anybody help ?

thanks in advance..

NEW POST: General Questions

mdressel — Mon, 29 Dec 2008 08:36:48 GMT

Currently, the solution uses a field named "SecureFieldStorageField" to store the data entered by the user, which is a text field. If you want to just change all Secure Fields to a date feild type, you would need to change the data type of this field. This could be done by modifying SecureField.cs and specifically the method EnsureSecureFieldStorageListExists. Then you would also need to change both SecureFieldEditor and SecureFieldControl to work with the new data type.

If you want to make the Secure Field solution work with multiple field types at the same time I would recommend a different approach but it would be much more complex.

bonzi wrote:
how do i change the data type of the this column. I plan to use a date in the secured column.

Regards
Sanjay

NEW POST: General Questions

bonzi — Mon, 22 Dec 2008 17:04:02 GMT

how do i change the data type of the this column. I plan to use a date in the secured column.

Regards
Sanjay

NEW POST: General Questions

mdressel — Mon, 08 Dec 2008 01:32:41 GMT

This should work with versioning. However, it was not explicitly tested.

mdressel wrote:
Questions pulled from the main page:

kvirani - Should this work with versioning enabled lists?

NEW POST: General Questions

mdressel — Fri, 05 Dec 2008 20:56:26 GMT

Questions pulled from the main page:

kvirani - Should this work with versioning enabled lists?

NEW POST: General Questions

mdressel — Fri, 05 Dec 2008 20:56:06 GMT

Questions pulled from the main page:

panoone - Any idea as to whether there are plans to get it into the core implementation for next point release of MOSS?

NEW POST: General Questions

mdressel — Fri, 05 Dec 2008 20:48:59 GMT

If there are general questions about the solution please post them here and we will provide responses where possible.

UPDATED WIKI: Home

Grzegorz — Mon, 24 Nov 2008 23:12:13 GMT

SharePoint - Secure Field
Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 support a rich security model that allows administrators to control access to sites and content by assigning permissions to users and groups for a specific securable object (such as site, list, library, folder and even an individual document or item).

However, in certain scenarios there is a need to secure access to individual columns in lists or document libraries. Currently, SharePoint does not provide out of the box support for securing columns or views. A typical scenario that would require this might be a list that contains a broad spectrum of information about an employee or a client, where certain columns (salary, revenue to date, potential to promote, etc.) might ideally only be viewable by certain groups within the portal.

To address those scenarios, this paper describes a method to leverage SharePoint extensibility and built-in item to level security to allow applying column-level permissions to a custom field type. This is accomplished through the use of a lookup field as the column, with behind the scenes ties to another list that contains the secure values and a method to provision those values back to the lookup only for users with valid permissions.

The result is that in the view mode authorized users will see the content of a secure column as if it was a normal column, while unauthorized users will not see the content of the column at all. This different behavior is shown in Figure 1. Similarly, only authorized users will be able to access the content of a secure column in new and edit modes.

You can read the full article at http://www.infoq.com/articles/Dressel-Gogolowicz-wss-security.