Hi,
I've managed to get Sametime Meetings 11.5 up and running successfully on a K8s 1.17 cluster.
My main issue is that some colleagues who join meeting rooms are being shown as 'undefined'. I suspect this is because they have Connections/Sametime/Verse open in another browser tab and Meetings has logged them without prompting for passwords.
No matter whether they log out and back in from the meetings screen, close their browser, or even try private/incognito modes, they are always shown as undefined. I suspect the initial SSO attempt to join a room has been persisted somewhere, but I've no idea where.
Anyone got any ideas?
Kind regards
Heidi
There are no entries in the mongo db meeting.meetings for these 'undefined' users, even if they were the ones to start a new meeting.
for the affected users - test with an incognito window - this will help determine if it is a cookie collision issue or other problem (like a Business Card issue)
We would likely need to review some data - so please open a case so that we can directly assist you.
Thanks Anthony,
I have already tried with the incognito window thinking it might be cookie/JWT/Ltpa related.
Unfortunately, I cannot reproduce the issue with any other Domino users that I have access to.
Very strangely I have just had this with a customer today as well. One moment it was all working the next anyone who logs in they are listed as undefined. It gets stranger if you open a chat in the meeting it all works as it should comes through to the sametime client as the correct user so they are logged in with regard to the webchat stproxy part.
If I try to start a recording then that fails and looking at the logs it is because of the undefined status as well Its very annoying as this happened during the testing phase of handing the build over when it had been working all day.
All other aspects of Sametime are working outside the meetings.
This is exactly what we are experiencing also. The sametime chat shows the users name fine. In Meetings, undefined.
In my case the problem is to do with SSO. I have not fixed this yet but I can prove it, If I login to meetings then open another tab and login to the stproxy webchat then go back to the meetings tab and hit f5 to refresh the name changes from undefined to my actual name.
Once I have found out what is wrong with SSO I will let you know but worth checking if you get the same as I do by repeating the above.
Hi Richard,
It is exactly as you've described on our side of things as well.
I have a ticket open for this - I am in the process of obtaining the requested logs from users for support.
Cheers,
Heidi
I don't know if this is relevant, or it is just a display bug, but, with my own working user, when I start the browser and login directly to meetings, my name is shown as Heidi Harding. If I open the stproxy webchat first and then change to meetings, my name is shown in the notes abbreviated format eg Heidi Harding/befine/DE.
I get exactly the same thing as you Heidi. I have rebuilt the SSO parts and rebuilt the Meetings deployment with new JWTokens / Secrets but still the same issue. I know it is an SSO issue somewhere but everything in regard to SSO works with everything else apart from with the meetings.
Please open cases with us so we can determine the cause(s) and solution(s) as needed. thanks!
Hi Heidi,
Did you get anywhere with this as I have tried everything but still the same issue so before I raise a call I thought I would see if you had found or been given a solution yet.
Regards,
Richard
Hi Richard,
Unfortunately we've had to halt any further work on Meetings. We will maybe re-visit it at a later stage of its development.
Sorry, I couldn't be of any further assistance.
Regards
Heidi
I have the same issue and have tried everything...
Seems to be a start of a common fault. I have a call open with HCL support so if we find a solution I will post it here.
Same issue as well. Funnily enough, it just started working without any changes being made. Was just affecting my profile and others in my organisation were fine. Very strange.
The issue happens, then goes away, then re-occurs for one user. Everyone else is fine.
We've logged CS0187678.
Thanks,
There are a couple of possible reasons for this issue - we are tracking one possible fix that will result in a patch, but I need case(s) from anyone with the problem so that we can confirm the cause(s) and get this resolved.
Cormac - I have requested your case be sent directly to my attention for review.
Here is mine a raised last week CS0187266
apparently it’s gone to the dev team.
I have this one as well - thanks!