|
Thanks for your replies. Matt, The only instances I have running are *ADMIN (2001) and my server test instance (which, by the way, is on port 8011). Sorry, I forgot to mention we are running V5R2 and are (I hope) current with our PTFS. Ken, I have been working with AS/400 systems since 1989, and I worked a lot with Web Server/Web Commerce 400 about six years ago. Nevertheless, it has been only since last week that I have begun messing around with Apache. So yes, I am *really* a newbie in this area. I think of myself as an ?oldbie? (can I say that?) in the rest of IBM midrange systems, way back to the *gasp!* S/34. In any case, the *PUBLIC *authority for the folder where this particular HATS app resides is *EXCLUDE. Best regards, Luis Rodriguez. >------------------------------ > >message: 5 >date: Thu, 28 Oct 2004 18:47:50 -0700 >from: "Ken Slaugh" <ken.slaugh@xxxxxxxxxx> >subject: RE: [WEB400] Using validation lists > >I'm guessing... Newbie here too :-) > >Can you find the folder within the WRKLNK command to the IFS and change the >object permissions? *PUBLIC is just that, the public. Maybe by removing that >authority will challenge the user to authenticate. Just a guess, I'd have to >test it. > >Hth, Ken > >-----Original Message----- >From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On >Behalf Of Luis Rodriguez >Sent: Wednesday, October 27, 2004 1:24 PM >To: web400@xxxxxxxxxxxx >Subject: [WEB400] Using validation lists > >Hi all, > >Warning: newbie in iSeries Web enablement :-) > >I am using a validation list to access my server. If I use >http://myserver:80, it asks for userid & password (ok!!). Nevertheless, if I >change my port to say, http:/myserver:9080/xx/entry (as in a HATS >project) and enter this address directly, it acceses it directly (no user id >prompt). > >How can I avoid this?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.