on 11-17-2016 11:55 AM
Hi All,
I have configured a destination as below. This destination is consumed in a HTML5 application hosted on my HCP account. Functionalities works fine in the HTML5 application for the initial token generated and until the initial token does not expire. Leave the app open on a browser for 20 mins without any activity, the token expires and the app is unresponsive. A manual browser refresh is required now but ideally the token should be regenerated on expiration of the old token. I have the below questions now:
1.) What is the default token expiration time? Would regeneration of token be the responsibility of HCP destination or HTML5 dispatcher?
2.) If yes, what property am i missing in the below configuration to ensure token gets auto refreshed based on expiry of old token? Or am i missing any other steps? Please advise
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.