...
We've set up a module in ServiceNow for using authenticated QuickBase tables as a data import sources in ServiceNow. The standard HTTPS and REST modules in ServiceNow can't easily do this--they only seem to support basic authentication, and the QuickBase API implements its own authentication system using an ephemeral session tokens. That means that the valid endpoint URL is periodically changing; this modification automatically maintains it for you.
...
Finally, there is a scheduled job that updates the session token and URL on an hourly basis. An update to a QuickBase Resource cascades to all data sources using it.
Downloads
[note terms of LICENSE]
| Attachments | ||
|---|---|---|
|
Related Documentation
...
- QuickBaseAuth object: implements a method for retrieving a new ticket from a set of credentials and a named target instance
Code Block /** * returns an array containing the ticket (index 0) and any error messages (index 1) * prototype => getTicket: function(instance, username, password) */ h2. Access Control * QuickBase Resources only visible to admin, since there is hot data (passwords, app tokens) // example: var qa = new QuickBaseAuth(); var result = qa.getTicket('mydomain.quickbase.com', 'myusername', 'mypassword'); ticket = result[0]; error = result[1];
...
- both refresh tickets (one explicitly, one on a schedule). Ticket
- ticket generation and scheduled refresh is hard-coded based on for one-hour tickets.
Access Control
- QuickBase Resources only visible to admin, since there is hot data (passwords, app tokens)