An API login session is created from two possible sources:
XML-RPC API login (Documentation)
SOAP Web Services login (Used in XTM, MemoQ integrations)
In both cases the login session is identified by the "API" column in the Statistics page:
...
One common issue is the possibility to retain the API functionality and be able to access TermWeb in a standard way at the same time without problems. For that matter a concurrent session option has been introduced.
...
API concurrent session option allows the coexistence of the two sessions for the same user, the API and the standard one:
...
This option lets the user use TermWeb via an external integration module (like MemoQ plugin) and at the same time open a browser and access TermWeb normally.
...
An example of session-specific hyperlinks for viewing and editing a term is the following:
...
There is an additional session that is registered in TermWeb, when accessing the application via a session-specific hyperlink.
...
One can see both sessions in Statistics page as API sessions with exactly the same attributes:
...
The reason for this additional session:
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 |
|---|
Suggestions for TermWeb Integration/Plugin usageWhen using TermWeb at the same time with a TermWeb Integration/Plugin, then the following actions are suggested for a smoother and easier workflow:
|