RE: [WEB400] V5R3 - Original Servers gone, completely!

["Jones, John (US)" <John.Jones@xxxxxxxxxx>]

I'm now up under SSL.  For V5R1 the REMOTE_USER variable is still valid.
We'll see what happens when we move to V5R3 later this year.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787  F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: Jones, John (US) 
Sent: Friday, September 24, 2004 12:38 PM
To: Web Enabling the AS400 / iSeries
Subject: RE: [WEB400] V5R3 - Original Servers gone, completely!

After the migration, I started the Apache instance and it came up OK.
The authentication worked but the net.data macros that retrieve the user
profile name (as an environment variable) weren't getting the profile
name returned.  This one little thing is what I've spent the morning
working on.  The online doc floats from V5R1 to R2 to the net.data site
to ignite400.com.  Eventually I found a link to a list of the
environment variables that appeared to be fairly current:
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/info/rzaie/rzaieenvvar
.htm  But all that showed was that what I was using, REMOTE_USER, should
be valid.  Reading the scant detail revealed that the script needed to
be protected.  OK, I thought it would inherit that since the whole site
is protected but apparently not.  I've made the change and my macros now
work as they did under the Cern version.

Unfortunately, REMOTE_USER, according to the link above, doesn't work
for SSL sites and part two of my migration is to SSL-enable the site.
So now that I have a working config, I'm about to break it again.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787  F: +1-312-601-1782
john.jones@xxxxxxxxxx



This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.