WASD WATCH & username/pwd

[Wim Van den Wyngaert]

I use WASD via IE.

WASD is started with /promiscous.

I access the WATCH utility.

From time to time it asks a username / password.

My config of WASD for this utility is the default one.

Questions :

Based upon what mapping the authorization is asked ?

Where is the username / password kept (I asked to keep them) ? I checked all files on VMS but didn't find it and my IE is rather closed by the company so I can't check if it's kept there.

What is the frequency of the password asking ?

Wim

[Karl Rohwedder]

The access is controlled via entries in HTTPD$AUTH, if memory serves me right. I'm on christmas holiday already and haven't configured WATCH... at home.

regards Kalle

[Wim Van den Wyngaert]

Kalle,

That's what I thought too. But I only find
[PROMISCOUS]
/cgi-bin/qdlogstats read

in it.

Wim

[Karl Rohwedder]

If I were at work, I could have a look into our HTTPD$AUTH, we made some changes...

Pls. have a look at the technical guide chapter 19.2 Access authorization here:
http://wasd.vsm.com.au/ht_root/doc/htd/

regards Kalle

[Wim Van den Wyngaert]

Here is a WATCH trace I was able to capture (I opened 2 times IE).

The question on the frequency is : after each start of IE. Where is it kept ? Not in a cookie.

I don't understand the syntax/reason/origin of :
[PROMISCUOUS;-;-] - R+W ; - -|

Still confused.

Wim

[Wim Van den Wyngaert]

The bug got me again.
The enclosure.

Wim

[Wim Van den Wyngaert]

Think I got it.

The application itselfs requests that authorization is done (in php "auth_user" is tested, in CGI too).

Wim

[Willem Grooters]

Wim,

This might well be the standard behaviour if started /promiscuous. Like the documentation states: this usually just a mode for testing.
I think the lifetime of a user-name password is about 1 minute or so.
It has NOTHING to do with mapping. HTTPD$AUTH may, or may not be involved. I think it's not (but I'm running "production" and so I cannot tell for now)

Willem.