Issue 22902 - Disable "Enforce click-through"
Summary: Disable "Enforce click-through"
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Upgrade (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: jobin1
QA Contact: issues@www
URL:
Keywords:
Depends on: 22446
Blocks:
  Show dependency tree
 
Reported: 2003-11-26 19:18 UTC by stx123
Modified: 2003-12-22 18:05 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description stx123 2003-11-26 19:18:22 UTC 
Please disable "Enforce click-through" as requested in the configuration check 
list.
Comment 1 kerry 2003-11-28 20:41:57 UTC 
Yes, this has been done.  The "enforce click-through" flag was 
*mistakenly* enabled during this last staging.  We will be doing 
another staging internally next week just to make sure that this 
doesn't happen when we upgrade production.

Since is done, I'll resolve this as fixed.
Comment 2 stx123 2003-12-02 11:17:49 UTC 
We would like to verify issues. Please let us know when an OOo server
is available to verification.
Comment 3 stx123 2003-12-07 09:38:40 UTC 
not fixed
Comment 4 jobin1 2003-12-07 19:30:36 UTC 
There may be some confusion here as I look at the history of this issue.  Click 
thru for *new* users is a contractual requirement of Sun Microsystems.  All 
*new* users must click thru the terms of use as required by Sun. While a single 
trip through the click thru screen may be annoying, we are complying with the 
terms of the Sun contract.

Above, Kerry was referring to forcing existing users to re-click thru after the 
upgrade.  To our knowledge, our testing has proven that no existing (migrated) 
users are challenged to re-click thru.  If a re-click thru for an existing user 
can reproduced, this is an issue for CN resolution.
Comment 5 Martin Hollmichel 2003-12-07 19:38:43 UTC 
ok, will resolve confusion internally
Comment 6 stx123 2003-12-22 18:05:07 UTC 
closing, the behaviour is now satisfactory.