How can I change the expiration length of a one time ticket? It is set to expire at 5 minutes by default. I need it set to 20 Minutes.

  • 0
  • 1
  • Question
  • Updated 3 years ago
  • Answered
Photo of Andrew

Andrew

  • 0 Points

Posted 3 years ago

  • 0
  • 1
Photo of Harrison Hersch (MCF)

Harrison Hersch (MCF), Champion

  • 40 Points
You cannot change that. You could use API_Authenticate and/or simply renew the ticket.
Photo of John

John

  • 0 Points
If I need to open a one time ticket and the process that needs to take place before they close the ticket takes longer than 5 minutes what would my options be?
Photo of Harrison Hersch (MCF)

Harrison Hersch (MCF), Champion

  • 40 Points
The simplest method would be to retrieve a longer ticket before the process starts.
Photo of John

John

  • 0 Points
So in this instance it would no longer be a "Onetimeticket" it would be another ticket type where you could set the expiration length? FYI I do work with MCF and I do have a ticket open with Kevin on this. I am just a little confused because I opened this ticket before and your team could not reproduce the error.
Photo of Harrison Hersch (MCF)

Harrison Hersch (MCF), Champion

  • 40 Points
If this is client-side code, you would not need a ticket. If this is server-side code, we get into some fairly complex processes managing ticket lifecycles for security practices. If you can shoot me an e-mail (hhersch@mcftech.com), I can jump in and help resolve this so we can retain confidentiality on the public forum. I'm happy to then contribute any findings to the community.
Photo of Harrison Hersch (MCF)

Harrison Hersch (MCF), Champion

  • 40 Points
We were able to resolve this with the client but it might be helpful information for the community if we elaborate more on the situation. If you experience similar issues, the following may be helpful.

In this specific scenario, the user pressed a button inside of QuickBase which launched them into a custom server-side script. This tool was intended to be used in one "shot", meaning opening the tool, perform the tasks and submit which would close it. Some users were clicking the home button on their iPad navigating away from the browser. Due to the way the iPad handles multi-tasking, the page was reloaded when the user went back into the browser. The iPad then reloaded the page without going through the intended lifecycle - so there was no new session with the server and the ticket was never renewed.

This issue was able to be resolved by working with the end users who were exiting the browser on the iPad.