Increase DTM's session time to more than 30 minutes

[#1]

Right now, the session length for http://dtm.adobe.com is only 30 minutes. 

Imagine this scenario:

1. Log into Tag Manager
2. Set up a rule
3. Go to paste a tag in, realize that you don't have it in proper form. 

• Shoot an email off to a dev OR
• Dig through your inbox, get a little distracted by another thread OR
• Go to the third party tool, log in, set up tool, copy tag

4. Paste tag, hit submit.

5. Get sent to the DTM login page.

6.Swear, log in again, repeat steps.

As you can imagine, 30 minutes isn't really long enough to properly fit into a typical workflow, and I find that after submitting a change, I'm logged out more than I'm logged in. Any change we can bump it up?

[#2]

Keeping the user logged in is really needed in dynamic tag manager.

Nothing worse than performing an action, after being away for +-30min, DTM will automatically log you out.

This is really annoying! 

If i want to log out then i will use the log out option.

I do understant that it is there for security purposes but there are other ways to prevent someone from using your account. A one time password is an otpion, google authenticator for example which can be enabled on your email and other google products.

[#3]

I think we need to merge the promotes on this idea:

http://ideas.omniture.com/t5/Idea-Exchange-for-Adobe/Increase-DTM-s-session-time-to-more-t han-30-minutes/idi-p/13731

So you can see how many people in total are annoyed by this!

[#4]

Hi Danielle,

Thank you for your comment and i am really glad that i am not alone.

I have encountered a loging screen many times after savings.

I woudl think that either as a default it automatically keeps you logged in until you decide to signout or you as a user can increase your timeout delay.

PS: love how you describe your flow

[#5]

@benjamingaines is there any where else we should be putting DTM ideas? This is such a small fix that would save hours of misery.

[#6]

Thanks for your input. 

Security is a primary focus for DTM. Making sure that your DTM access dosen't fall into the wrong hands is something we take very seriously. Currently, our security team has dictated the 30 minute timeout. We'll bring it up to the team again, but please know that its current setting was determined with your company's security in mind. 

[#7]

Thanks for your input. 

Security is a primary focus for DTM. Making sure that your DTM access dosen't fall into the wrong hands is something we take very seriously. Currently, our security team has dictated the 30 minute timeout. We'll bring it up to the team again, but please know that its current setting was determined with your company's security in mind. 

[#8]

If the session timeout could not be based on a new page loading, that would help. Currently, if the user is working on custom code for more than 30 minutes, that counts as a timeout- when you click to save your 30+ minutes of code work, the save doesn't happen because of the session timeout. 
I can understand 30 minutes of true inactively, but if the user is making changes in a rule/custom code block for over 30 minutes, that shouldn't count as "inactive"

[#9]

Since there is a security aspect to this, but Jenn is mentioning a good point with editing rules/code, what about a popup that comes up with a minute or two left before the session expires to see if you want to extend your session?

[#10]

I agree, this is super annoying.  Too many times I HAVE been actively working on a rule, code within a rule, etc.. and many times it takes longer than 30m and when I go to click the Save button, BAM, redirected to login screen and all my hard work is GONE.  This is SUPER frustrating.  

I understand timing the session out if the user is TRULY inactive but simply checking for the last top level ping (e.g. from Save or Cancel etc. buttons) is not good enough.  It is not that hard to implement additional ajax calls for smaller actions like opening code windows etc. to refresh the timeout.  PLEASE do this.