[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] user authentication and user dependent services
|
Hi Scott,
Am 01.07.2015 um 17:16 schrieb Scott Lewis:
On 6/30/2015 11:21 PM, Peter Hermsdorf wrote:
If I've understood your use case correctly (above questions), then I
can think of a couple of approaches. One that I've done myself is to
have some other OSGi service for storing/retrieving the association
between the clientID and the username/pw/auth info. Then you could
store that association away upon connect/disconnect (or at some other
point in the protocol...e.g. if you have some other login service),
and then look it up/check it in response to a remote call. There is
a way with existing API to get the clientID/fromID for every remote
call.
That might be a way. But then I need some API to get the clientID of
the "current" caller to find the authentication information that got
stored on login....
The IRemoteServiceCallPolicy interface has the clientID that is the
'containerID of the remote caller', so it is passed to those that
implement that interface.
That would work for me and I will implement a small service that does
the resolving to the current user.
Thanks!
