Idm Download Timeout

[Mariela Laflam]

WhenI'm logged into OSTicket and it's been idle for a while (not sure exactly how long...15-30min?) and I try to create a new ticket or click on one etc., OSTicket recognizes that I've been inactive for a certain period of time and proceeds to log me out.

I had "Staff session timeout" set to 2000 (that should be minutes) and even with that, a staff user could be kicked out even after just 10 minutes. Then I switched it to 0 and today I've received another complaint. I wonder if it's hardcoded somehow?

@[deleted] this thread is from July 2008 and version 1.6ST. This version has not only reached end of life but has not been supported for a couple years now. You should upgrade if you are using this version due to a number of security reasons. I also doubt that you are going to receive any answer(s) beyond this one.

Hoping someone might have a solution to the approval timeout. I have created a few approval flows, majority are approved within the 30 days once triggered. However, there is still the odd occasion a longer timeout would be helpful. Is there any work around to increase the 30 days once triggered?

The 30 days is for the overall flow, but it resets every time you restart the flow. If you are doing a serial approval you'll have to do something to make sure you don't resend the first approval after a restart if you restart on the second or third.

There is no way to extend the timeout for a specific flow beyond 30 days. The workaround is to set the approval action timeout for 29 days and when it times out the action use the Run after settings to re-start the approval flow via an HTTP call. This will resend the approval email, so the approver will now have two emails, and it requires a premium license.

I'm running a script with the Python tool in Alteryx, however, it quits after 30s. I get the error [NbConvertApp] ERROR Timeout waiting for execute reply (30s). At least, I think that's the problem (see complete error message below. After browsing the interwebs, as one does, I noticed that it's possible to increase the timeout time (link). How can I do this with the Alteryx Python tool. Can I change something in one of the .py files in site-packages? Which one? And most important, will changing that solve my issue?

I am trying to run checks on my data using the new Python tool. Everything is working as expected when I select a small number of rows, but once I use the whole data (approximately 1M rows) I am getting a timeout error "Timeout waiting for execute reply (30s)". Is there a way to adjust the Python configurations to increase the timeout waiting time?

@PaulN Is there anyway to change the timeout for a particular app? I've changed the base code so that the default timeout is -1, and now I want a particular app to have a 60 second timeout. I'm running this on the gallery. Is there a way to modify the app so that the python tool in it errors out after 60 seconds?

I have it up and running, BUT was dealing with some issues with a test workstation being disconnected within minutes of logging on, even though I had "Dead Entry Timeout" selected on the STAS Suite for 2 hours (for testing). Within minutes of logging on, (and showing up under "Live Connections" the workstation would suddenly drop off the list. If I "logoff" or even "Lock" the workstation and log back in... it works again for a few minutes.

After working with support for some time, I noticed if I set "Dead entry timeout" on the AD Domain Controllers STAS Suite to 0 (disabled) this not longer happened and the user would stay connected indefinitely. Previously had it set for 2 hours (just for testing).

Question to you guys MUCH smarter than I: What is the most FOOL PROOF, dependable, way to setup SSO w/ AD authentication (As far as logging off workstations that sit idle for an extended period)?

NOTE: whatever settings I use, I am trying to avoid adding exceptions or software to the workstations (just do to limited time, and creating more possible issues/security holes). Just want a reliable solution that is stable and easy to implement.

I think is a good configuration to go with but, the perfect one will only come after several permutations; learning the need in your network. This shall give you an inch inside the reporting section alongside, it will also automatically sign out the users after 9 hours.

Logoff Detection using ping is what i use now. It's much easier to deal with than wmi and won't drop user's internet after X hours. Dead entry timeout will drop user after X hours, then it depends on wmi query to get user back unless user logoff and login another time.

Client base authentication is much better since they didn't rely on network access of wmi. I use authication client everyday and never have a problem. But SSO Client is complete broken currently (user get kicked off for no reason every minute).

On my old SonicWall, I use to use LDAP integrated w/ Active Directory. It has worked well, but did require a separate login for Firewall access (something that some of my users struggled with). And I did have some security/certificate issues w/ Browser upgrades and Certificate issues. (so I thought I would try something different)

On Sophos XG (Configure>Authentication>STAS) "Enable User Inactivity" w/ Inactive Timer (example: Inactivity:360 minutes / 256byte "Data Transfer Threshold") (MY understanding: This will watch user activity and if a user is "inactive" for more than 360 minutes, it will log the user OUT of the Sophos XG "Live Connections" list ONLY.

On DC's (BOTH) set "Dead Entry Timeout" set for (example: 9 hours) (My Understanding: This remove the user from the "Live Users" table after 9 hours of log in). Clearing them out of the "Live Users" database). ODD thing: During testing I set this for 1 hours (Dead Entry Timeout), but as long as the Sophos XG showed the user under "Live Connections" the would not get logged out, UNTIL the sophos XG would remove them from the "Live Connections" list, then the user would fall off the "Show Live Users" list on DC's STAS Suite. Not sure if I was doing something wrong, for I thought the two: ("Dead Entry Timeout, and XG "Enable User Inactivity") do not necessarily work together... I think?

daiqingxu: When you say "Client Based Authentication" do you mean you loaded the Client on all of your workstations? I was thinking this would be a lot of worn (1 man IT department) and possibly cause issues Security/Performance, (loading more software on workstations)?

You can load the client with authication client or sso client with gpo. sso client is broken so you can't use it. authication client will require user to enber their credential once then it can remember it and login automatically. If users already familiar with login through some thing, it maybe the best choice. it use heart beat to detect user logout, which is most reliable solution i believe.

Unlock with PIN: On mobile apps, the PIN is a string of numerical digits (of any length), but in all the other client apps (vault, desktop, browser extension), the PIN can contain any combination of upper/lower-case letters, numbers, and special characters. Thus, you can in effect set an alternate password that is easier to type than your master password.

I know I can do a passwordless login on the web vault (Log in with device) where a prompt comes up on my iPhone to allow the login instead of using the master password. That may work for you? I enabled it on my iPhone and iPad.

I think passwordless login is the future.

You will find that Bitwarden is a lot more safety-conscious than other password managers, and this behaviour is by design. Unless you set your vault to Never timeout (which is not recommended), the key to your vault is stored in protected memory by your browser extension. When you close your browser, that memory is deleted and you lose your key, so you have to login again.

I think what most people do is lock their vault and leave their browser running in the background, since typing in a PIN to unlock is much more convenient that typing in your master password each time. Or, if you have biometrics enabled on your device, you can use that instead.

The code works very nicely when I use under 900 averages but when I increase the Averages I get a Visa read time out error, because the default time (2000 ms) Is not high enough. I tried to set it to 10000 ms, but it still doesn't work. Could anyone help me with this issue? Thank you so much!

2. Although your For Loop runs 3 times, only the data in the last iteration gets saved. Why? You are opening and closing the file inside the loop. They should probably be done outside of the loop. As a result, when it reopens, and the file pointer is at the beginning by default, data is written from there, overwriting all of your previous data.

Thank you both so much for your replies! As suggested I tried to adjust the VISA buffer - however, even if I leave the buffer input values as default (screenshot) I get an error message that the buffer mask is invald? I also tried all the other buffer masks (32, 48) but with no success. Any help would be highly appreciated

3. Essentially, the REC: SETUP: START 3 command recalls a specific setup in the oscilloscope with all the settings I need. Unfortunately, it is not possible to recall a setup which includes averages, this is why I included a 'configure acquisition field' afterwards where I can set the number of averages. The number of averages I need is 5000 but currently the maximum I can acquire is 900, after that I get a Visa timeout error.

We're actually working on rolling this functionality out in the next couple of weeks. If you're open to beta testing it, send me an email (dmitriy at retool) and I'll connect you with the engineer that's working on it!

I appreciate the opportunity to join the beta but tbh this wasn't an ongoing issue for me. It was an initial set up thing so I just added logging & re ran from a new start point a number of times until the work was done. Thankfully the called iteration doesn't time out at 15min, that continues until it's finished (presumably with a 10 or 15 min timeout).

3a8082e126