in ConnectSession Login Event missing?

[Former Community Member]

I am using ConnectSession to implement authentication,

and I want to wait for its login Event before I let my code
to move on ...

but I don't LOGIN event is exposed, I did found
_sessionManager dispatching LOGIN but again its internal



in api docs SessionEvent states LOGIN event constant but cant
find a public class that dispatches it.



can ConnectSession dispatch LOGIN event at the end of onLogin
method?

[Raff_]

The authenticator (AdobeHSAuthenticator, or whatever you are
using) does fire a LOGIN_SUCCESS / LOGIN_FAILURE event. Wouldn't
that be enough for your usecase ?

[Former Community Member]

I am using AdobeHSAuthenticator, but only for token, and I am
using ConnectSession to initiate login



_conSeason.login(),

and since conSeasonis the one initiating login, would not it
make more sense for to dispatch login event as well. ( its my
objective idea, might be wrong :) )

[Former Community Member]

Hi,

We normally do our code to move on after we receive the
SynchronizationChange event from connectSession as you will see in
LoginDialog Example. After the onLogin function in ConnectSession,
its best to wait for the messagemanager and the four
sharedManagers(user/room/file/stream) to get synchronized, before
we draw any UI involving cocomo components as they depend on the
sharedManagers.

So, is not listening to SynchronizationChange event solves
your purpose. As far as the dispatching of SessionEvent.Login is
concerned , we will definitely keep that in find fr future.



Thanks

Regards

Hironmay Basu

[Former Community Member]

quote:

---

Originally posted by:
Hironmay

Hi,

We normally do our code to move on after we receive the
SynchronizationChange event from connectSession as you will see in
LoginDialog Example. After the onLogin function in ConnectSession,
its best to wait for the messagemanager and the four
sharedManagers(user/room/file/stream) to get synchronized, before
we draw any UI involving cocomo components as they depend on the
sharedManagers.

So, is not listening to SynchronizationChange event solves
your purpose. As far as the dispatching of SessionEvent.Login is
concerned , we will definitely keep that in find fr future.



Thanks

Regards

Hironmay Basu

---

yes that will definitely work, thanks for the tip and thanks
for this great product.