Ok, so it sounds like you now understand that STAF handles are associated 
with each STAFProc instance running on a machine.  When a STAF service 
request is submitted to a remote machine, information about the 
handle/machine that originated the request is provided in the request 
information, including user authentication information if the handle has 
been authenticated, but STAF handles themselves are not "shared".  Each 
STAFProc instance has it's own STAF handles (with handle 1 always assigned 
to STAFProc itself).

--------------------------------------------------------------
Sharon Lucas
IBM Austin,   luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313




From:   agou <a...@talktalk.net>
To:     staf <staf-users@lists.sourceforge.net>, 
Date:   01/10/2012 12:08 AM
Subject:        Re: [staf-users] Delegated service gives 
"HandleManager::updateTimestamp() failed to update handle"



Hi Sharon, and thanks for taking the time.

Well I don't have problems with delegating as such, it clearly works 
in itself; the delegated service receives the requests as expected.

I use a static handle because I need to use user trust, and I think I 
must have misunderstood the way this works. I had the idea that when I 
authenticated a user against a handle, then this authenticated handle 
would be a sort of network wide "security token" that would be 
transported around all over the place, in a sense.

What happens in my setup is that a request starts on, say, fox, as a 
request to my service on local. This is forwarded to a central server, 
hag, where it is interpreted and as a result a number of other service 
requests are sent out to other servers. I have assumed that I could - 
or should - do this using the same handle all the way, but I realise 
now that this is probably wrong.

In fact, I have since tried it with tracing turned on, and I can see 
that the message comes from hag, not from fox.

/jan

Sharon Lucas wrote:
> I have no problems delegating the LOG service on a Linux machine 
(staf1e) 
> to an AIX machine (aixclient) and accessing it. 
> 

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users


------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users

Reply via email to