Skip to main content link. Accesskey S
  • Anonymous
  • Log on
  • Help
  • IBM logo
  • IBM Forms wiki
  • All Wikis
  • Home
  • Community Articles
  • Product Documentation
  • Learning Center


Search

Advanced Search

Categories

Tag Cloud

  • 3.0
  • 3.5
  • 3.5.1
  • 4.0
  • 4.0.0.1
  • 4.0.0.2
  • 8.0
  • accessibility
  • actions
  • API
  • app dev
  • button item
  • buttons
  • C
  • certificates
  • COM
  • compute
  • computes
  • configuring
  • creating
  • defining
  • demonstration
  • demos
  • deployment
  • deployment scenario
  • design
  • design tips
  • Designer
  • designing
  • dev guide
  • develop
  • developing
  • differences between Webform Server and Viewer
  • education
  • Enablement
  • enterprise
  • error messages
  • events
  • field
  • field item
  • FileNet
  • filtering
  • form
  • formatting
  • forms
  • forms experience builder
  • Forms Services Platform
  • FSP
  • functions
  • getting_started
  • Help
  • IBM Forms
  • images
  • installing
  • integrating
  • integrating, 4.0.0.1
  • items
  • JAVA
  • JavaScript API
  • language
  • languages
  • layout
  • lf_intro
  • math functions
  • methods
  • new_user
  • options
  • P8
  • performance
  • pipelines
  • pipes
  • printing
  • programming
  • Properties
  • samples
  • services
  • signature item
  • signatures
  • spec
  • string functions
  • strings
  • StrJava
  • submissions
  • table
  • tables
  • text
  • training
  • translation
  • Turbo
  • turbo_media
  • tutorials
  • utility functions
  • video
  • Viewer
  • viewer package
  • Webform Server
  • WebformServer
  • XFDL
  • XForms
  • XPath
InformationInformation
You are currently viewing machine translated content. IBM translation might be available. Click IBM Translated Product Documentation to see what is available.X


Home > Best Practices for Form Design > Sign related items
Rate this article 1 starRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

Sign related items 

expanded Abstract
collapsed Abstract
No abstract provided.



Many items point to another item for their values, images, and help messages. These items are considered related. Related items include lists, popups, and comboboxes with cells, buttons and images, or any item linked to a help message. For the best security, when you sign an item, you must sign all related items.

If there is a conflict between signed and unsigned items, you must err on the side of signing. For example, you can omit a cell group for a popup, but if two popups use the same cell group and only one popup is signed, then the cell group should still be signed.

This is important to prevent accidental modification of the signed item. If a signature signs only one item in a related pair of items, the unsigned item can be modified. For example, someone could alter unsigned cell information even when the related popup item has been signed. As a result, the content of the form could be changed after the user has signed it.

While an omit filter automatically signs all items and options that you do not specifically exclude, keep filters must explicitly list all items and options you want to secure. Because related items often do not appear as separate items on the form, it is easy to neglect them in your keep filter. If you are using keep filters, always double-check that you are securing all related items. For example, images are stored in separate data items. Items that display images simply contain references to the data item. Therefore, if you secure a button using a keep filter but forget to secure the image data, the button's image is not secured and could be modified.

Example


Assume you are creating a popup with the following two choices visible to the user:

"Please do not sell my personal information"
"You may sell my personal information"

When the users sign the form, the popup is secured with a keep filter that does not specify the popup's cells.

Once a choice is selected, the scope identifier (sid) of the cell containing the choice is stored in the popup's value option. In this example, assume the user chooses "Please do not sell my personal information". The sid of this choice is cell1. The secured popup stores a reference to cell1 in it's value option. This secures the sid of the popup, preventing users from selecting a new cell from the popup. However, the cell itself is not signed. A malicious user could open the form in a text editor and change the text contained in cell1 so that it no longer reflects the choice made by the user. For example, the cell's value could be changed to "You may sell my personal information". Anyone viewing the form after this alteration would think that the user permitted the company to sell her personal information.

Exceptions to this practice


There are no exceptions to this practice that you should consider

Note:
While there are no exceptions to this practice, you should be aware that conflict resolution between signed and unsigned items must err on the side of signing. For example, you can omit a cell group for a popup, but if two popups use the same cell group and only one popup is signed, then the cell group should still be signed.

expanded Article information
collapsed Article information
Category:
Best Practices for Form Design, Forms Designer, Webform Server, Forms Viewer, Signature Best Practices,
Tags:
security, signatures

This Version: Version 7 December 2, 2010 6:09:57 PM by Jack Mitchell  IBMer

expanded Attachments (0)
collapsed Attachments (0)

 


expanded Versions (7)
collapsed Versions (7)
Version Comparison     
Version Date Changed by               Summary of changes
This version (7) Dec 2, 2010 6:09:57 PM Jack Mitchell  
6 Apr 15, 2009 5:11:06 PM Deanna Drschiwiski  
5 Sep 8, 2008 2:58:19 PM Deanna Drschiwiski  
4 Jul 7, 2008 12:54:13 PM Deanna Drschiwiski  
3 Jun 12, 2008 2:09:35 PM Adam Kozyniak  
2 Jun 10, 2008 6:22:13 PM Adam Kozyniak  
1 Jun 9, 2008 7:23:10 PM Adam Kozyniak  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedSubscribe to RSSHelpAbout
  • All Lotus and WebSphere Portal wikis
  • IBM developerWorks
  • IBM Software support
  • IBM Social Business User Experience Blog
  • IBMSocialBizUX on Twitter
  • IBMSocialBizUX on Facebook
  • Lotus product forums
  • IBM Social Business UX blog
  • IBM Collaboration Solutions
  • Recently added feedRecently added
  • Recently edited feedRecently edited
  • Recently added comments feedRecently Added Comments
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Contact IBM
  • IBM Terms of use
  • Wiki terms of use