Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

UserManager.removeUser

Avatar

Level 4

hey guys

apologies for all the questions, hope you don't mind (can you tell i'm english? ) really appreciate the help!

anyway: scenario:

1. dave opens a session

2. dave invites bill

3. bill comes in

4. bill is drunk & abusive so dave runs his goddam @$$ outta the room UserManager.removeUser(billsUserID);

5. over on bills machine there are listeners listening to SessionEvent.SYNCHRONIZATION_CHANGE, ConnectSessionEvent.CLOSE, SessionEvent.ERROR, Event.ACTIVATE & Event.DEACTIVATE

6. but only the SessionEvent.SYNCHRONIZATION_CHANGE listener is run

7. the SessionEvent.userDescriptor prop is null

i was expecting / hoping that this SessionEvent.userDescriptor would have a valid UserDescriptor that would be Bills so i could go "Uh, Bill, it's YOU Dave has kicked out, so we'd better end ur local session and remove ur pods etc mate". but no cigar, boo! 

am i listening to the right thing? or... what do i need to do over on Bill machine to pick up the fact that Bill has been kicked out?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hey Dubya,

UserManager.UserBooted should do the trick. Only the user kicked out should receive it.

nigel

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Hey Dubya,

UserManager.UserBooted should do the trick. Only the user kicked out should receive it.

nigel

Avatar

Level 4

nigel, that has totally sorted it. that user has been so forcibly removed from the room he's scared of ever coming back again. RESULT !

thanks mate 

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----