Gerry,
RedBack uses a request/response model.
Each RedBack request(e.g. setting or getting a property or actioning a
method on a RedBack object) is considered to be a single atomic action and
is picked up by the first available RedBack responder. There is no concept
of a user or session in the
Thanks for the replies.
Let me ask a related question - maybe the question I should have asked in 1st
place ;)
My universe su solution works just peachy for terminal sessions. The new
request was raised with regards to the clients web interface. Of course the
common logon scenario doesn't
requirement.
thanks
Gerry
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Mike Randall
Sent: Tuesday, December 07, 2004 09:02 AM
To: [EMAIL PROTECTED]
Subject: RE: [U2] [ot] hpux11/uv10 validate user login
Not true. Redback database requests are handled
requirement.
thanks
Gerry
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Mike Randall
Sent: Tuesday, December 07, 2004 09:02 AM
To: [EMAIL PROTECTED]
Subject: RE: [U2] [ot] hpux11/uv10 validate user login
Not true. Redback database requests are handled
Gerry,
Their web interface is driven built on redback I have zero experience with or knowledge of it. I would have thought os(unix) level user authentication would have been handled within redback as part of its basic design/functionality. True or not true ?
Your problem is a security issue.
Hi Gerry,
have you considered using LDAP? On AIX you can LDAP authenticate against
the local user database so I presume HPUX can do something similar.
Then use an ldap client (I believe curl would work or one of the
openldap utilities) to authenticate (be aware that passing passwords in
