Hi Nick.

It turns out, my other asyncio loop was conflicting with the one in platform_session.py (I am on 1.0.0a0).

Because of this conflict, I was not able to get any values when calling PlatformSession.get_last_event_code() and PlatformSession.get_last_event_message() were returning 'None'.

I think, rdp library platform_session.py should be changed from:

def run(self):
    self._loop = asyncio.new_event_loop()
    asyncio.set_event_loop(self._loop)

To

def run(self):
    try:
        self._loop = asyncio.get_event_loop()
    except RuntimeError:
        self._loop = asyncio.new_event_loop()

This way, when I call PlatformSession.get_last_event_code() and PlatformSession.get_last_event_message(), they return valid values related to the token/session:

EventCode.SessionAuthenticationFailed
iPlanet session has been expired.

I am by no means an asyncio expert, is this something you could raise with the developers? I could not find a github repository for the rdp library to raise this issue.

Thanks

Hi @JIAN.DU

Can you confirm if you are using the session state event handlers e.g.

rdp.PlatformSession(
    app_key,
    rdp.GrantPassword(
    username = user,
    password = password),
    on_state = lambda session, state, message : print("Platform session state: ", state, message),
    on_event = lambda session, event, message : print("Platform session event: ", event, message))

The same can be done for Eikon/desktop and TREP sessions as well.

Also, my colleague will do some test around authentication with the latest version of RDP library and respond once completed.

Hi @JIAN.DU,

The behavior I would expect you should get is that on A, when the application attempts to refresh its access token, a session authentication event should be raised within the Session indicating an issue. In this scenario, did you mistakenly start an application on server B? Or did you want the application on server B to assume control of authentication? Or did you expect the application on server A to steal it back?