SECURITY USER_AUTH IN UBBCONFIG FILE

Question

My question regarding this is: if you set this option, what kind of security do we
need? Do we need a process to be running? The problem I have is that I created a
Tuxedo /WS client. The only way to get it running is to comment this out. I have
added code to try to validate that is something like this:
strcpy(tpinfo-->usrname, (char *) "sa");
strcpy(tpinfo-->cltname, (char *) "clarify");
strcpy(tpinfo-->passwd, (char *) "sa");
strcpy(tpinfo-->grpinfo, "");
This always fails. In our test region, I can logon as "sa"..can someone explain
a little how security works?

Answer 1

When you use USER_AUTH security you also need to specify a value
for the AUTHSVC parameter in the ubbconfig.
Every time a client calls tpinit() this service will be called
with the TPINIT data you supply to tpinit().
If the service returns with TPSUCCESS the client will be granted
access to the system, else it will be denied.
You can write this service yourself. If you do, you must put it
in a TUXEDO server (like any other TUXEDO service) and make sure
that the server is running (it should have an entry in the
*SERVERS section in ubbconfig).
If you don't want to implement this service BEA supplies a
"standard" version called .AUTHSVC in a server named AUTHSVR.
In this case you should make sure that AUTHSVR is in the
*SERVERS section of the ubbconfig. If you use this server you
also need to maintain the "database" for that server, using
tpusradd and similar commands.
Please note that you will still need to supply an application
password that is common to all clients, similar to APP_PW
security.
Hope this helps,
/Per
"Joe" <[email protected]> wrote:
>
My question regarding this is: if you set this option, what kind of security
do we
need? Do we need a process to be running? The problem I have is that I
created a
Tuxedo /WS client. The only way to get it running is to comment this out.
I have
added code to try to validate that is something like this:
strcpy(tpinfo-->usrname, (char *) "sa");
strcpy(tpinfo-->cltname, (char *) "clarify");
strcpy(tpinfo-->passwd, (char *) "sa");
strcpy(tpinfo-->grpinfo, "");
This always fails. In our test region, I can logon as "sa"..can someone
explain
a little how security works?