Acrobat Forms Question - Secure Form Handling

I'll preface this post by saying I'm not a designer nor have I ever designed an Acrobat form. If the following is possible, I'll probably have to find a developer to do it for me.
I have a small business that needs to receive and pass around by email a completed Acrobat form with sensitive personal data in it. I want to know if it's possible to do the following:
User goes online and opens the form with Acrobat Reader (assume Windows and Mac platform users).
User enters the data required in the form.
When data entry is complete, user clicks a button toward the bottom of the form that applies a predetermined password to the form. I predetermine the password and it will be coded into the form. The password will be required to open and print. Ideally two passwords exist each with a different security level. One allows only to open and read the completed form. The other password allows opening and printing.
Once the form is password protected, they can then click a button in the form to email it to a predetermined email address.
Again, assume the user entering the data into the form only has Reader, not full Acrobat.
Is this possible?
Thanks.
Andrew

No, not all of that is possible, not even with Acrobat. When you have to transmit data securely without the user somehow encrypting the data, it's easiest to get a web server involved. The data can be securely transmitted (via HTPS/SSL) and stored, but it does involve a bit of server-side programming as well as setting up the form. You also have the option of just transmitting the form data, as opposed to the entire PDF. When you transmit the entire PDF with Reader, the document has to be Reader-enabled, which comes with licensing restrictions on the number of times you can use data from a particular form. This is not an issue when just sending the form data, which can be imported by you into a blank form whenever needed.

Similar Messages

Acrobat Forms Question

Hi there,
Quick question on forms, I created some forms in Acrobat, but when the user fills them out, they can't save and email them, it doesn't let them, how do I remove this protection?
Thanks!

Acrobat 7.0.9 also lets your users reply to forms with User Rights Enabled (albeit a bit more work in the process in Acrobat 7.0.9 than in 8 ). But it works.

Using container managed form-based security in JSF

h1. Using container managed, form-based security in a JSF web app.
A Practical Solution
h2. {color:#993300}*But first, some background on the problem*{color}
The Form components available in JSF will not let you specify the target action, everything is a post-back. When using container security, however, you have to specifically submit to the magic action j_security_check to trigger authentication. This means that the only way to do this in a JSF page is to use an HTML form tag enclosed in verbatim tags. This has the side effect that the post is not handled by JSF at all meaning you can't take advantage of normal JSF functionality such as validators, plus you have a horrible chimera of a page containing both markup and components. This screws up things like skinning. ([credit to Duncan Mills in this 2 years old article|http://groundside.com/blog/DuncanMills.php?title=j2ee_security_a_jsf_based_login_form&more=1&c=1&tb=1&pb=1]).
In this solution, I will use a pure JSF page as the login page that the end user interacts with. This page will simply gather the input for the username and password and pass that on to a plain old jsp proxy to do the actual submit. This will avoid the whole problem of having to use verbatim tags or a mixture of JSF and JSP in the user view.
h2. {color:#993300}*Step 1: Configure the Security Realm in the Web App Container*{color}
What is a container? A container is basically a security framework that is implemented directly by whatever app server you are running, in my case Glassfish v2ur2 that comes with Netbeans 6.1. Your container can have multiple security realms. Each realm manages a definition of the security "*principles*" that are defined to interact with your application. A security principle is basically just a user of the system that is defined by three fields:
- Username
- Group
- Password
The security realm can be set up to authenticate using a simple file, or through JDBC, or LDAP, and more. In my case, I am using a "file" based realm. The users are statically defined directly through the app server interface. Here's how to do it (on Glassfish):
1. Start up your app server and log into the admin interface (http://localhost:4848)
2. Drill down into Configuration > Security > Realms.
3. Here you will see the default realms defined on the server. Drill down into the file realm.
4. There is no need to change any of the default settings. Click the Manage Users button.
5. Create a new user by entering username/password.
Note: If you enter a group name then you will be able to define permissions based on group in your app, which is much more usefull in a real app.
I entered a group named "Users" since my app will only have one set of permissions and all users should be authenticated and treated the same.
That way I will be able to set permissions to resources for the "Users" group that will apply to all users that have this group assigned.
TIP: After you get everything working, you can hook it all up to JDBC instead of "file" so that you can manage your users in a database.
h2. {color:#993300}*Step 2: Create the project*{color}
Since I'm a newbie to JSF, I am using Netbeans 6.1 so that I can play around with all of the fancy Visual Web JavaServer Faces components and the visual designer.
1. Start by creating a new Visual Web JSF project.
2. Next, create a new subfolder under your web root called "secure". This is the folder that we will define a Security Constraint for in a later step, so that any user trying to access any page in this folder will be redirected to a login page to sign in, if they haven't already.
h2. {color:#993300}*Step 3: Create the JSF and JSP files*{color}
In my very simple project I have 3 pages set up. Create the following files using the default templates in Netbeans 6.1:
1. login.jsp (A Visual Web JSF file)
2. loginproxy.jspx (A plain JSPX file)
3. secure/securepage.jsp (A Visual Web JSF file... Note that it is in the sub-folder named secure)
Code follows for each of the files:
h3. {color:#ff6600}*First we need to add a navigation rule to faces-config.xml:*{color}
    <navigation-rule>
<from-view-id>/login.jsp</from-view-id>
        <navigation-case>
<from-outcome>loginproxy</from-outcome>
<to-view-id>/loginproxy.jspx</to-view-id>
        </navigation-case>
    </navigation-rule>
NOTE: This navigation rule simply forwards the request to loginproxy.jspx whenever the user clicks the submit button. The button1_action() method below returns the "loginproxy" case to make this happen.
h3. {color:#ff6600}*login.jsp -- A very simple Visual Web JSF file with two input fields and a button:*{color}
<?xml version="1.0" encoding="UTF-8"?>
<jsp:root version="2.1"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:jsp="http://java.sun.com/JSP/Page"
xmlns:webuijsf="http://www.sun.com/webui/webuijsf">
    <jsp:directive.page
contentType="text/html;charset=UTF-8"
pageEncoding="UTF-8"/>
    <f:view>
        <webuijsf:page
id="page1">
<webuijsf:html id="html1">
<webuijsf:head id="head1">
<webuijsf:link id="link1"
url="/resources/stylesheet.css"/>
</webuijsf:head>
<webuijsf:body id="body1" style="-rave-layout: grid">
<webuijsf:form id="form1">
<webuijsf:textField binding="#{login.username}"
id="username" style="position: absolute; left: 216px; top:
96px"/>
<webuijsf:passwordField binding="#{login.password}" id="password"
style="left: 216px; top: 144px; position: absolute"/>
<webuijsf:button actionExpression="#{login.button1_action}"
id="button1" style="position: absolute; left: 216px; top:
216px" text="GO"/>
</webuijsf:form>
</webuijsf:body>
</webuijsf:html>
        </webuijsf:page>
    </f:view>
</jsp:root>h3. *login.java -- implent the
button1_action() method in the login.java backing bean*
    public String button1_action() {
        setValue("#{requestScope.username}",
(String)username.getValue());
setValue("#{requestScope.password}", (String)password.getValue());
        return "loginproxy";
    }h3. {color:#ff6600}*loginproxy.jspx -- a login proxy that the user never sees. The onload="document.forms[0].submit()" automatically submits the form as soon as it is rendered in the browser.*{color}
{code}
<?xml version="1.0" encoding="UTF-8"?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page"
version="2.0">
<jsp:output omit-xml-declaration="true" doctype-root-element="HTML"
doctype-system="http://www.w3.org/TR/html4/loose.dtd"
doctype-public="-W3CDTD HTML 4.01 Transitional//EN"/>
<jsp:directive.page contentType="text/html"
pageEncoding="UTF-8"/>
<html>
<head> <meta
http-equiv="Content-Type" content="text/html;
charset=UTF-8"/>
<title>Logging in...</title>
</head>
<body
onload="document.forms[0].submit()">
<form
action="j_security_check" method="POST">
<input type="hidden" name="j_username"
value="${requestScope.username}" />
<input type="hidden" name="j_password"
value="${requestScope.password}" />
</form>
</body>
</html>
</jsp:root>
{code}
h3. {color:#ff6600}*secure/securepage.jsp -- A simple JSF{color}
target page, placed in the secure folder to test access*
{code}
<?xml version="1.0" encoding="UTF-8"?>
<jsp:root version="2.1"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:jsp="http://java.sun.com/JSP/Page" xmlns:webuijsf="http://www.sun.com/webui/webuijsf">
<jsp:directive.page
contentType="text/html;charset=UTF-8"
pageEncoding="UTF-8"/>
<f:view>
<webuijsf:page
id="page1">
<webuijsf:html id="html1">
<webuijsf:head id="head1">
<webuijsf:link id="link1"
url="/resources/stylesheet.css"/>
</webuijsf:head>
<webuijsf:body id="body1" style="-rave-layout: grid">
<webuijsf:form id="form1">
<webuijsf:staticText id="staticText1" style="position:
absolute; left: 168px; top: 144px" text="A Secure Page"/>
</webuijsf:form>
</webuijsf:body>
</webuijsf:html>
</webuijsf:page>
</f:view>
</jsp:root>
{code}
h2. {color:#993300}*_Step 4: Configure Declarative Security_*{color}
This type of security is called +declarative+ because it is not configured programatically. It is configured by declaring all of the relevant parameters in the configuration files: *web.xml* and *sun-web.xml*. Once you have it configured, the container (application server and java framework) already have the implementation to make everything work for you.
*web.xml will be used to define:*
- Type of security - We will be using "form based". The loginpage.jsp we created will be set as both the login and error page.
- Security Roles - The security role defined here will be mapped (in sun-web.xml) to users or groups.
- Security Constraints - A security constraint defines the resource(s) that is being secured, and which Roles are able to authenticate to them.
*sun-web.xml will be used to define:*
- This is where you map a Role to the Users or Groups that are allowed to use it.
+I know this is confusing the first time, but basically it works like this:+
*Security Constraint for a URL* -> mapped to -> *Role* -> mapped to -> *Users & Groups*
h3. {color:#ff6600}*web.xml -- here's the relevant section:*{color}
{code}
<security-constraint>
<display-name>SecurityConstraint</display-name>
<web-resource-collection>
<web-resource-name>SecurePages</web-resource-name>
<description/>
<url-pattern>/faces/secure/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
<http-method>HEAD</http-method>
<http-method>PUT</http-method>
<http-method>OPTIONS</http-method>
<http-method>TRACE</http-method>
<http-method>DELETE</http-method>
</web-resource-collection>
<auth-constraint>
<description/>
<role-name>User</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<realm-name/>
<form-login-config>
<form-login-page>/faces/login.jsp</form-login-page>
<form-error-page>/faces/login.jsp</form-error-page>
</form-login-config>
</login-config>
<security-role>
<description/>
<role-name>User</role-name>
</security-role>
{code}
h3. {color:#ff6600}*sun-web.xml -- here's the relevant section:*{color}
{code}
<security-role-mapping>
<role-name>User</role-name>
<group-name>Users</group-name>
</security-role-mapping>
{code}
h3. {color:#ff6600}*Almost done!!!*{color}
h2. {color:#993300}*_Step 5: A couple of minor "Gotcha's"_ *{color}
h3. {color:#ff6600}*_Gotcha #1_*{color}
You need to configure the "welcome page" in web.xml to point to faces/secure/securepage.jsp ... Note that there is *_no_* leading / ... If you put a / in there it will barf all over itself .
h3. {color:#ff6600}*_Gotcha #2_*{color}
Note that we set the <form-login-page> in web.xml to /faces/login.jsp ... Note the leading / ... This time, you NEED the leading slash, or the server will gag.
*DONE!!!*
h2. {color:#993300}*_Here's how it works:_*{color}
1. The user requests the a page from your context (http://localhost/MyLogin/)
2. The servlet forwards the request to the welcome page: faces/secure/securepage.jsp
3. faces/secure/securepage.jsp has a security constraint defined, so the servlet checks to see if the user is authenticated for the session.
4. Of course the user is not authenticated since this is the first request, so the servlet forwards the request to the login page we configured in web.xml (/faces/login.jsp).
5. The user enters username and password and clicks a button to submit.
6. The button's action method stores away the username and password in the request scope.
7. The button returns "loginproxy" navigation case which tells the navigation handler to forward the request to loginproxy.jspx
8. loginproxy.jspx renders a blank page to the user which has hidden username and password fields.
9. The hidden username and password fields grab the username and password variables from the request scope.
10. The loginproxy page is automatically submitted with the magic action "j_security_check"
11. j_security_check notifies the container that authentication needs to be intercepted and handled.
12. The container authenticates the user credentials.
13. If the credentials fail, the container forwards the request to the login.jsp page.
14. If the credentials pass, the container forwards the request to *+the last protected resource that was attempted.+*
+Note the last point! I don't know how, but no matter how many times you fail authentication, the container remembers the last page that triggered authentication and once you finally succeed the container forwards your request there!!!!+
+The user is now at the secure welcome page.+
If you have read this far, I thank you for your time, and I seriously question your ability to ration your time pragmatically.
Kerry Randolph

If you want login security on your web app, this is one way to do it. (the easiest way i have seen).
This method allows you to create a custom login form and error page using JSF.
The container handles the actual authentication and protection of the resources based on what you declare in web.xml and sun-web.xml.
This example uses a statically defined user/password, stored in a file, but you can also configure JDBC realm in Glassfish, so that that users can register for access and your program can store the username/passwrod in a database.
I'm new to programming, so none of this may be a good practice, or may not be secure at all.
I really don't know what I'm doing, but I'm learning, and this has been the easiest way that I have found to add authentication to a web app, without having to write the login modules yourself.
Another benefit, and I think this is key ***You don't have to include any extra code in the pages that you want to protect*** The container manages this for you, based on the constraints you declare in web.xml.
So basically you set it up to protect certain folders, then when any user tries to access pages in that folder, they are required to authenticate.
--Kerry

Adobe Acrobat 9.0 - PDF form to email

I have created an employment application form that I would like to post on our website and have the applicants email back to us. Is it possible to with Adobe Acrobat 9.0 and the submit button? I have tried this but I think I am missing something. I have also created this in Lifecycle Designer but found that it will only email xml. We would like to receive the pdf itself if it is possible. Any help would be greatly appreciated.
Thanks,
Christine

The submit process would be more like "maito:name@domain". There are important "features" you need to be aware of.
1. For Reader users to submit the full form you must activate Reader Rights -- a potential problem if you expect the form use to exceed 500 over the years.
2. There is no need to submit the full form, but simply import the XML (then you developed the form in Designer and questions should really go to the LiveCycle forum in the future) in to the form on your end. The result will be the same as the full form.
3. E-mail is not a secure form of submission and included personal data on an e-mail submitted form may land you into some legal trouble eventually. I said may, not will -- but it is something to keep in mind.
4. E-mail capabilities vary with the client machine and may fail, making you appear as a fool even if it is a client problem.
5. Compatibility with prior versions of Reader and Acrobat is a good idea, since many folks do not upgrade to the latest version.
In general I would recommend submission to a web script (you will need some IT help there) with the XML format that you simply import to the form. Do not activate Reader Rights and simply allow the client to print the form for their records instead.

Acrobat Reader 9 with an Acrobat 5-8 Created Form?

Hello,
I am new to my job working with a ASP application that provides a PDF form (created in Acrobat 5) to users with free form fields the user can fill out. Users have been complaining that when the users upgrade to Acrobat Reader 9 the begin to see a message that "Some features are no longer supported..." and the ability to save a local copy of the file is no longer available. I have 2 questions.
Was the ability to save a local copy of a form with user-entered data ever a feature of Acrobat Reader?
Is that an issue that can be corrected by creating the form with the Acrobat 9 Life-Cycle engine or is that a feature that has forever been removed from Acrobat Reader for security or other reasons?
Thanks in advance!
- Yohancef

No I was referring to filled in forms.
So to be clear, the ability to save user filled in information in a form to your local machine as a PDF through Acrobat Reader IS possible, but has to be enabled by opening the form in Acrobat (9 for example) and enabling some feature to allows Reader users to save the information to the PDF file. This feature is limited though and has a 500 use limit per form.
Does that sound correct? Do you know the name of the feature?
Thanks!
Yohancef Chin
Date: Mon, 2 Nov 2009 16:49:54 -0700
From: [email protected]
To: [email protected]
Subject: Acrobat Reader 9 with an Acrobat 5-8 Created Form?
There may be some features that are not supported any more but you may not be using them. That message is just a general warning.
As far as saving the filled in form, Reader on it's own has never been able to do it. You would need the newer version of Acrobat to open and enable these forms so that Reader users can save them. Be warned that this feature is meant for small-time use and has a usage limit of 500 submissions per form. You'll want to read and undestand the EULA before planning on using it.
Or do you mean that they cannot save the unfilled form either?
>

Cannot distribute secured form.

Hi Everyone,
Using Livecycle Designer ES2 9, with Acrobat Pro 10.0.3. Standalone implementation.
When attempting to distribute a secured form, Acrobat displays "Acrobat is unable to distribute this form because of the form's security settings."
The form distibutes and functions perfectly without security, but we require the code to be secured. What am I missing?
Thanks,
Ron

Everyone,
Check this discussion/question http://forums.adobe.com/message/3689326#3689326
Ron

How do I add a functional "submit button" to a pdf form in Adobe Acrobat Pro XI ? I created the pdf form in Adobe Forms Central.

How do I add a functional "submit button" to a pdf form in Adobe Acrobat Pro XI ? I created the pdf form in Adobe Forms Central. It's for an online Diet Questionnaire. After people complete the form I'd like them to click "SUBMIT" and the completed form will be emailed to me.

This can be a bit confusing because Acrobat 11 comes with the desktop app that allows you to create simple PDF forms without having a FormsCentral account. Some people find this helpful, but you need to understand that when you generate the PDF form, it is Reader-enabled by Acrobat. In order to edit the form further in Acrobat, you have to create a non-enabled copy of the form. You do this in Acrobat by opening the form and selecting: File > Save a Copy
and opening the copy. It is not opened automatically.
You can now add a button and set it up to submit by email, either using a "Submit a form" action or the submitForm JavaScript method. You can set it up to include just the form data or the entire PDF, and will want to use a mailto type URL. Submitting the form to the FormsCentral server has a number of important advantages over email (much more reliable, more secure, etc.), so you might want to consider it.
If the form needs to be saved with Reader versions prior to 11, then you will need to Reader-enable the document. In Acrobat 11 you do this by selecting: File > Save As Other > Reader Extended PDF > Enable More Tools

Form based security in WebLogic 7.0

I'm sorry for the beginner level question, but I seem to be missing a critical step
in getting Form based security to work. I have a Web application comprised of several
JSPs. I want to attache simple FORM based security contrainsts to all pages in the
app. Here are the exceprts from my web.xml:
<security-constraint>
<web-resource-collection>
<web-resource-name>DTSTAT</web-resource-name>
<url-pattern>/StateServlet/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>Sysops</role-name>
</auth-constraint>
<user-data-constraint>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<form-login-config>
<form-login-page>/StateServlet/login.html</form-login-page>
<form-error-page>/StateServlet/login-error.html</form-error-page>
</form-login-config>
</login-config>
<security-role>
<role-name>Sysops</role-name>
</security-role>
The app deploys correctly and I have verified that the constrinsts, etc. are recognized
by WebLogic by inspecting the content displayed from the Admin console under the
"Edit Web Apllication Deployment Descriptor" link - all looks as I had expected and
matches the XML configuration above.
I then use the "Define Resources and Roles for Web Resource Collections" link. Under
the "Define Policies" section I see the constraints as defined above. I then use
the "Define Roles" link to define the "Sysops" role for this application and add
the condition "Caller is a member of the group" and use Administrators as the Group.
From this point, I invoke one of the JSPS in the app and presented with the Login
page as expected. However, no matter what I enter for user and password, I always
get the login-error page back. I'm purposely trying to keep this simple so that
I can use the system user as a test case (who is a member of the Administartors group).
However, I have also created an additional separate user and added them to the Administartors
group as well with the same unsuccessful results.
Can anyone help me out please? I've been reading the docs and seem to be missing
a key element somewhere.
Thanks in advance,
Todd

          Try to refer to the documentation for
          Configuring Security in Web Applications at
          http://e-docs.bea.com/wls/docs70///webapp/security.html
          Does the weblogic.log file contain any error or warning
          messages corresponding to your problem ?
          If you have a test case to reproduce the problem, you
          can contact BEA support at [email protected]
          Thanks
          Developer Relations Engineer

Saving a filled-in secure form in Reader?

Apologies if this has been covered somewhere in the forums. I've just not been able to find anything that answers this...
I've created a form for a client in Acrobat 9 Pro. Security is set to allow printing and "Filling in form fields and signing existing signature fields." My problems begin when opening the form in Reader X.
The instructions in Reader says "Click 'Sign' to fill out and sign this form. When you are done, you can save a copy by clicking 'Done Signing'"
I click "Sign" and fill-in the form fields. However, "Done Signing" never turns live in the sidebar. It remains grayed-out. The only option available is to "Send Signed Document" using Adobe's EchoSign system. However, doing so simply sends a blank form, with none of the fields filled-in.
Save As... doesn't appear to be an option either, as it will only save a blank copy of the form.
How does a user fill-in and save a secured form in Reader X? Will I have to remove all security from the form altogether? Or is a user doomed to have to use EchoSign...which apparently only saves a blank version?
Side observation: That sidebar is very confusing to the user. What's "Add Text" for? It could easily be assumed that the user needs to click that in order to fill-in the fields. And, there's no need for anyone to sign or "Place Signature" in this form. How can a user avoid this altogether?

If it needs to be saved with Reader, the document has to be Reader-enabled. To do this with Acrobat 10, select: File > Save As > Reader Extended PDF > Enable Additional Features
The EchoSign related stuff in Reader should be ignored for a form like this.
Note that Reader 11, which will be released shortly, is able to save a non-enabled form, but not if the form uses digital signatures. If it does, it will need to be Reader-enabled.

HT4009 I'm attempting to down load an app by the name of hudmaniax,upon entering my password for purchase approval I'm prompted to re enter my password a second time followed up with a form to create a security form ...I.e name of first school attended e

I'm attempting to down load an app by the name of hudmaniax,upon entering my password for purchase approval I'm prompted to re enter my password a second time followed up with a form to create a security form ...I.e name of first school attended etc etC.

This is normal behaviour. Apple have recently introduced increased security to protect you from fraudulent transactions. Once you have answered the questions (remember your answers) you will only be asked for them occasionally in future.

Creating Secured Forms and Saving Completed Forms

Hi,
I have been tasked by my manager to create a checklist form which me and my colleagues must complete and save when carrying out servicing of various medical equipment. For this, I have been using Adobe Acrobat Professional 6, using the forms feature. I created the form with various form fields and secured the pdf file with a password, only allowing the form fields to be filled in. However, when the user opens the file in Adobe Acrobat Reader, they can fill in the form but cannot save it as another file, it only allows them to print it. Ideally, what I would like for the user to do is to open up the template form, allowing them to fill in the form fields without being able to edit the document and then save the completed form with the job number as the file name. Is there any way to have the document secured but also allow the 'save as' button to be used? I would be extremely grateful if you could help :-)
Thanks,
Michael

You can upgrade from AA6. Keep in mind it is a good idea to keep your AA6 CD around even after the install of AA9. If you have problems in the future and have to reinstall, you will need the AA6 CD or at least the information from it. You can check the Adobe store for information about the update.
It sounds like your application would be within the bounds of the EULA as I read it. If you have fewer than 500 folks who will be using the form, then by the EULA you are allowed to activate Reader Rights. As I read the EULA, they can do multiple submissions of the form and such, just as long as the number of users stays below 500. You may want to read the EULA before the upgrade to be sure you will be in compliance (the EULA can usually be found on the Adobe site).
Starting with AA8, Reader Rights was an added feature that could be used to allow users of the Reader to save the form with the data.

Hide password and user name fields in secure form on landing page

On a landing page I don't want the password or user name displayed in the "secure" form because I think it will keep people from downloading our e-book. It will cause what some refer to as too much friction—visitors will feel that we are asking too much of them just to download an e-book so won't do it.
I found somewhere where the user name can be populated with the e-mail address, although I couldn't figure out where to put the code to make it work.
Can the password fields also be auto-populated and hidden so the user can access the secure zone to download the e-book never even knowing that they had a user name and password assigned to them?
I'd really appreciate some help here and please keep in mind that html and css is where my expertise stops so if there is a java solution I will need the code and how and where to add it.
Many thanks for your help.
John

This article just might point you in the right direction: http://kb.worldsecuresystems.com/853/cpsid_85381.html

Master-Detail Form Questions

Master-Detail Form Questions
I have two questions in regards to master-detail forms:
First, the form I am working on has 25 detail rows displayed to the user. If the user has more than 25 detail records for the master, I want them to be able to add more. For instance, after they enter the 25th record, I would like a pop up window to ask them if they would like to add more detail records for this master. If they select yes, then the records they have entered would be saved and then the form would repopulate with the current master record and another empty 25 detail records.
Second, I would like the Detail Action to be set to Insert if the user moves to a new detail row and selects an item from a combo box.
Thanks for any and all help.
Jeremy.

Hi Sharmila.
Is there a way to repopulate only the Master information without populating the detail after the 'Save' button is pressed? I have written code that uses the session variables and repopulates the form with all the data that has just been saved, but I need only the master without the detail.
Thanks.

Form based security in WebLogic 7.0 - back button quirk

I have an application comprised of several JSPs that are protected via Form based
security and enforce an SSL connection via the appropriate declarations in the
web.xml. This aspect of the application seems to be working with the exception
of one small quirk.
If a user presses that back button until such time as the receive the container
provided login page once again, and subsequently provide a valid user id and password,
they are NOT successfully logged in. Rather, they receive the ugly 403 Forbidden
error that states that the server understood the request, but is refusing to fufill
it. This only seems to happen given the above course of events involving the
use of a back button in the browser (or selection of an item from the history
list). I suspect that this has something to do with the session id being cached
or something, but I'm not sure? Can anyone offer any assistance on this one?
Also, does anyone know of a way of preventing the user from bookmarking this container
provided login page as this also seems to be causing problems for users. If they
bookmark the first protected page of the application all is fine, but if they
bookmark the login page they receive the 403 error.
Thanks in advance!

The cure for the symtops described below was to simply add a welcome-file-list
element with appropriate welcome pages to the web.xml descriptor. It makes sense
now that I have worked it out.
Todd
"Todd Gould" <[email protected]> wrote:
>
I have an application comprised of several JSPs that are protected via
Form based
security and enforce an SSL connection via the appropriate declarations
in the
web.xml. This aspect of the application seems to be working with the
exception
of one small quirk.
If a user presses that back button until such time as the receive the
container
provided login page once again, and subsequently provide a valid user
id and password,
they are NOT successfully logged in. Rather, they receive the ugly 403
Forbidden
error that states that the server understood the request, but is refusing
to fufill
it. This only seems to happen given the above course of events involving
the
use of a back button in the browser (or selection of an item from the
history
list). I suspect that this has something to do with the session id being
cached
or something, but I'm not sure? Can anyone offer any assistance on this
one?
Also, does anyone know of a way of preventing the user from bookmarking
this container
provided login page as this also seems to be causing problems for users.
If they
bookmark the first protected page of the application all is fine, but
if they
bookmark the login page they receive the 403 error.
Thanks in advance!

How do I paste a signature onto an Acrobat XI Standard pdf form?

How do I paste a signature onto an Acrobat XI Standard pdf form?

Do you want a scribbled annotation, a facsimile stamp, a signature form field, or invisible certifying signature?

Acrobat Forms Question - Secure Form Handling

Similar Messages

Maybe you are looking for