Authentication & Payment
From ThirdPresence Wiki
Contents |
For video authentication and billing you can use
- Your own or 3rd authentication and payment system
- Thirdpresence provided authentication and payment provider
URL protection
Video URLs for paid content are unique for every end-user and have a short lifespan. The lifespan of the video URLs can be set to a custom value from 1 minute to 24 hours.
If the video URL that the end-user tries to access has expired, the end-user will be sent to the pre-defined authentication interface to get a new authorization.
3rd Party Authentication and Payment
Here is a description of the 3rd party authentication process.
The 3rd party payment and authentication is responsible for
- End-user authentication and credentials
- End-user subscriptions and user database management
- Payment processing
End-user Process Diagrams
API integration
API integration between ThirdPresence and 3rd party authentication system
Same as sequence
user customer site thirdpresence 3rd party authentication
select "watch video1"
--------------------->
user is redirected to authentication and payment
with contentid of video1.
----------------------------------------------->
authentication system generates [token]
and adds that with contentid
to thirdpresence system.
<----------------------
user is redirected to
thirdpresence with
[token] and contentid
<----------------------
"video1" starts from short lifespan url (if [token]
can be found at thirdpresence system)
<----------------------------------------------
Parameter passing between systems
The token authorization request documentation can be found here: Parameter passing via API.
When the end-user requests a video and authorization has been completed the token is added to the video URL as a query parameter: token=[token].
Example:
http://show.thirdpresence.com/dls/t/watch.jsp?iid=31733&token=[token]
No API integration
If there is no API integration between ThirdPresence and the 3rd party authentication system the process works as follows:
user customer site thirdpresence 3rd party authentication
select "watch video1"
--------------------->
"video1" url directs to
thirdpresence
----------------------->
user is redirected to
authentication and payment
with [unique token]
and stock keeping unit
---------------------->
user is redirected to
thirdpresence with
[unique token] and
auth/payment status
<----------------------
"video1" starts from short lifespan url
<----------------------------------------------
Parameter passing
When the end-user is redirected to the return URL provided by the authentication system, the authentication token and stock keeping unit (contentid) are passed as query parameters.
Example:
http://some.url/payment?url= http%3A2F%2Fshow.thirdpresence.com%2Fdls%2Ft%2Fwatch.jsp%3Fiid%3D31733 &sku=31733&token=[token]This page was last modified on 22 January 2013, at 08:43.