If you have your own database, along with a website that your clients already login to, you can use Title Remote Authentication along with the API method AuthenticateRemoteUser to avoid forcing your users to login for a second time to view your content hosted with us.

Step 1:  Setup remote authentication for your title (edit title>security>remote authentication)

Click Here for Article on Remote Authentication

This is a requirement, because we must take into account folks that may try to access the issue/title URL outside of the secure website area, in which we would display our login challenge.

That needs a custom script built that will take username/password POSTed from our system, and compare to your remote database, then return a value to our system indicating success or failure, to allow/block access.

Step 2:  Use the AuthenticateRemoteUser method to call our system to obtain a token

Click Here for the article on AuthenticateRemoteUser API Method

This method will return a token from our system that must be appended to your issue/title URLs on your secure page, and that token appended link will bypass the second login (our system).

An example method call could be:

(xxxxx is where you would need to plug in your API Key, Signature, and TitleID)

That method will return an XML response (or JSON if chosen) that contains a token. You must parse that XML response (or JSON) and add the token to the end of an issue/title URL that is on that secure webpage using ?token=xxxxx

You can dynamically build these token appended links whenever the secure page loads OR

Recommended:  Obtain and append the token on link click instead to reduce the number of API calls