Versions Compared

Old Version 18

changes.mady.by.user Stefanos Kargas

Saved on

compared with

New Version Current

changes.mady.by.user Stefanos Kargas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When opening a browser, an HTTP/HTTPS session is automatically created. TermWeb standard login uses this session as a TermWeb session, while an API session is created separately. When opening TermWeb in a browser via a hyperlink, the HTTP/HTTPS session is still created from the browser and it needs to be registered in TermWeb session manager along with the API session in order for the application to function correctly. However both sessions are linked together and always expire together when logging out or be manually removed. They are linked to the same active user. One does not need to worry about them, but consider them as one. Additionally, when registering this HTTP/HTTPS session in TermWeb, the session overwrites any existing standard session of the same user if it finds one. This is only logical, because the browser's HTTP/HTTPS session is now linked to the API session via the hyperlinks.

Info
titleSuggestions for TermWeb Integration/Plugin usage

When using TermWeb at the same time with a TermWeb Integration/Plugin, then the following actions are suggested for a smoother and easier workflow:

  • The API concurrent session option should be enabled, in order to avoid sudden logouts and error messages in case the users separately starts a standard login.
  • Before clicking on a session-specific hyperlink for the first time, the default browser should be closed, in order for the first HTTP/HTTPS session to be uniquely initialized for TermWeb without any conflicts.
  • When using an API session and a standard session with two different users at the same time, then the standard session should be opened in a different browser than the default, because in this case the HTTP/HTTPS session will be different than the one created from the hyperlinks and both sessions will not affect each other. For instance, if Chrome opens the plugin's hyperlinks, then the user can open Firefox and log into TermWeb using a different user, without the one session affecting the other.