This happens because the link from the displayed article goes directly against the TM server and does not go through Cx. Therefor TM has no idea of the user session. There probably only one solution for this
- Generate an SSO type token and make it part of the link URL that is used to fetch the article.
- Parse this URL and validate the token. if valid login the user.
This happens because the link from the displayed article goes directly against the TM server and does not go through Cx. Therefor TM has no idea of the user session. There probably only one solution for this