You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
connect is called all over the place in rfa.kaltura2.
It's designed to return a client (and session key) that can be used to communicate to the API, and it gets that session key through an authentication dance.
Instead of holding onto that session key and re-using it within the plone application (like save the session key it to the registry and re-use it to create more client connections) it asks for a new one on every call to kconnect() and re-does the authentication dance.
To make matters worse, kconnect() tells the kaltura server to keep that session key authorized for 86400 (one day) even though we throw it away and immediately ask for a new one on every call.
This is embarrassing and needs to be fixed.
The text was updated successfully, but these errors were encountered:
connect is called all over the place in rfa.kaltura2.
It's designed to return a client (and session key) that can be used to communicate to the API, and it gets that session key through an authentication dance.
Instead of holding onto that session key and re-using it within the plone application (like save the session key it to the registry and re-use it to create more client connections) it asks for a new one on every call to kconnect() and re-does the authentication dance.
To make matters worse, kconnect() tells the kaltura server to keep that session key authorized for 86400 (one day) even though we throw it away and immediately ask for a new one on every call.
This is embarrassing and needs to be fixed.
The text was updated successfully, but these errors were encountered: