• Replies 2 replies
  • Subscribers 1369 subscribers
  • Views 48 views
  • Users 0 members are here
Options
Related

Custom Screens - v15 - ability to change token keys

Vivek Mittal
$organization

Hi,

I'm trying to implement a browser based custom screen onto the constituent pages to show information from an external system.  The external system is a vendor provided out of the box solution that takes in a Sync_ID key with the value being the constituent id.  The Tessitura docs specify that they pass in "key" in the query string with the constituent id as the value.  Is there any way to rename key to sync_id?

The solution also requires an oauth token to be passed in that expires every 20 minutes.  Is there any way for Tessitura to generate that token and also pass that in as part of the URL to the browser based custom screen?

Regards,

Vivek

Parents
  • $organization

    Your first question should be fairly straightforward. You can specify whatever query parameter you like when you pass the key to your web app by just putting a uri like customwebapp.com/?sync_id=<<key>> in the custom screen setup panel.

    I'm not aware of a way to generate and pass an Oauth token via the custom screen feature. My first thought would be that you might need to build a custom middleware app between Tess and your external system to handle Oauth, but I'm also fairly new to working with the custom screens, so others might know more.

    Graham

  • $organization in reply to Graham Wright

    Thank you.  That was a simple answer.  I was thinking the URL was customwebapp.com/?key=xxxx.  I thought the parameter key was key; not that the value was <<key>>.  

    For the second part, I'm thinking along the same lines as you.  Have a middleware component that generates the token every x minutes and then updates the URL in the DB with the token.  However, not sure how that would be impacted by things like caching on the Tessitura app side - would it reload the URL every time the screen is refreshed so that a new updated token would be used.

    An alternative I was thinking was to develop an intermediary web app hosted somewhere locally that will receive the request from Tessitura and then, retrieve the token and invoke the final end-point.  Something like a proxy app... but that adds complexity in terms of another hop and finding somewhere to host it.

    Cheers,

    Vivek

Reply
  • $organization in reply to Graham Wright

    Thank you.  That was a simple answer.  I was thinking the URL was customwebapp.com/?key=xxxx.  I thought the parameter key was key; not that the value was <<key>>.  

    For the second part, I'm thinking along the same lines as you.  Have a middleware component that generates the token every x minutes and then updates the URL in the DB with the token.  However, not sure how that would be impacted by things like caching on the Tessitura app side - would it reload the URL every time the screen is refreshed so that a new updated token would be used.

    An alternative I was thinking was to develop an intermediary web app hosted somewhere locally that will receive the request from Tessitura and then, retrieve the token and invoke the final end-point.  Something like a proxy app... but that adds complexity in terms of another hop and finding somewhere to host it.

    Cheers,

    Vivek

Children
No Data