After changing ST_AUTH_TOKEN to Fork:Jwt,notes on the sametime community to set SSO with the meetings 11.5 server, SSO is broken with connections.
Login to the sametime web chat (the new one) -> successful login
Login to connections -> the login page is displayed
When inspecting the token used in the sametime client, the sso cookie do not contains reference to LtpaToken or LtpaToken2
if reverting back to ST_AUTH_TOKEN=notes, SSO is working again
Any idea?
Please open a case for this so we can investigate and resolve.
I had exactly the same problem.
Answer I received from HCL Support:
This is currently 'by design' as the Sametime Meeting Server is looking for the JWT token and does not support LTPA as an 'initial' login method.
Sametime Meeting Server is looking for the JWT token and does not support LTPA as an 'initial' login method. That being said - after the initial login to meetings - there will be two JWT Cookies added to the browser session - the JWT Token (2 hours) itself and the JWTREfresh token (30 days). The user should not be prompted to 'login' again as long as the JWTRefresh token is valid.
We have the same issue. We need the "LtpaToken" to get the profile pictures from Connections to the proxy server, which is currently not working anymore.
Case is opened.
Hello,
I have almost the same issue.
Each time I change the line from ST_AUTH_TOKEN=notes et ST_AUTH_TOKEN=Fork:Jwt,notes, my Sametime proxy integration fails and of course, I cannot connect to meeting.
How did you solve this problem ?
Best regards
I think I just responded to your case Luc -
Usually when this happens, it is due to an error loading the Jwt libraries - if you are on linux, ensure you are using the 'ststart' script to start/stop the community server.
https://help.hcltechsw.com/sametime/11.5/admin/starting_and_stopping_community_server.html?hl=ststart
Let me know.