Password logging in other areas except "Logins" section
Hello,
Love this product but one huge annoyance is that password changes are only logged when the entry is in the "Logins" section. Are there any plans to bring this awesome logging feature to the other sections that contain password information?
Thanks.
Comments are currently closed for this discussion. You can start a new one.
2 Posted by Stu Helm on 26 Mar, 2012 06:38 PM
I'm a little confused by what you mean here, only Login items can actually be updated via our browser extensions, what other items are you wanting 1Password to provide a password history for?
Stu Helm
Agile Crusader
AgileBits
http://support.agilebits.com
http://twitter.com/1Password
3 Posted by cyberzeus on 26 Mar, 2012 06:50 PM
Hi Stu,
So I am talking in the actual 1Password software - not via any browser extensions.
Within the actual application, passwords can be defined in the "Accounts" section as well as the "Login" section however, password changes and histories are logged in the latter section only. For several of my credential items, it makes more sense to have them stored in the "Accounts" section so it would be nice to have functional parity between both the "Logins" & "Accounts" sections…
Support Staff 4 Posted by Kyle Swank on 27 Mar, 2012 05:09 PM
Hi shop,
Thanks for the clarification. I wasn't around when this decision was made so I'm not sure what the rationale was but there may have been a really good reason for why.
I will make a note of this and see if we can't add this in the next major upgrade of 1Password. I can't make any promises but I will at least bring it up and make sure the idea is heard.
Cheers!
Kyle Swank
AgileBits Support
5 Posted by cyberzeus on 28 Mar, 2012 06:59 PM
Great - thanks Kyle - this would be a really awesome enhancement. Also, I did ponder for a bit on why this would have been left out but honestly, I cannot think of any credible reason so if you come across the real story, I would be curious to hear the rationale. I can't imagine this wold be hard to implement but then again, I didn't write the code so not completely sure.
Anyway, thanks again…and fingers crossed...
Support Staff 6 Posted by Kyle Swank on 29 Mar, 2012 02:16 PM
Hi,
I can't come up with a valid reason either, but I'm in the same boat as you and didn't write it so the answer is in the heads of the developers I'm sure.
I do like this feature though so hopefully we'll see it stick around and get moved into some other categories.
Thanks again for letting us know about your request. If you ever see something else you'd like to have in 1Password please let us know.
Have a fantastic week!
Cheers!
Kyle Swank
AgileBits Support
System closed this discussion on 07 Jun, 2012 10:20 PM.
cyberzeus re-opened this discussion on 21 Aug, 2012 12:35 AM
7 Posted by cyberzeus on 21 Aug, 2012 12:35 AM
Hello Agile Team,
Has there been any movement on this as a new feature inclusion?
8 Posted by Stu Helm on 21 Aug, 2012 12:47 AM
We don't generally comment on or promise if or when a feature request will be a part of future 1Password plans, so while Kyle has certainly passed on the request we can make no promises as to if or when it may be part of 1Password.
Stu Helm
Agile Crusader
AgileBits
http://support.agilebits.com
http://twitter.com/1Password
9 Posted by cyberzeus on 21 Aug, 2012 01:07 AM
Truly unfortunate - it's always a good idea to share the future with your customers beyond just the security stuff. Most software companies do this at some level and while agreed that making firm commitments is a double-edged sword, keeping dark lights on the future is not a good SOP.
This is something your mgmt team should consider changing...
Support Staff 10 Posted by Kyle Swank on 21 Aug, 2012 01:15 PM
Hi there,
It's more than just time commitments. We hate saying we'll include something, then see it not make the cut. It has happened in the past and we've been burned by it. So, now we simply don't comment on new features until they arrive. It sets expectations.
We also have customers who will buy our product based on what it may be in the future, not what it is now, then be disappointed when we said feature x will be available, but still isn't. That they bought our app because of that feature.
I hope you can see the reasoning. We just set up disappointment by saying we'll include anything at all. We'd rather under promise and over deliver, than do the reverse.
I really am sorry for the trouble.
Cheers!
Kyle Swank
AgileBits Support
11 Posted by Peter Clark on 31 Aug, 2012 09:37 PM
Wanted to give a +1 to this feature request - I just hit the same problem when updating a system account password on a machine that cares about password history. I'm keeping that account info in the Accounts area, just like the original poster. Since I use 1password for all my passwords (not just browser auto-fill), having the history recorded in the Accounts section would be really useful.
I'd also want to have the ability to have pronouncable generated passwords be configured to include caps and/or punctuation, to be in compliance with the Windows Server complexity rules described here:
http://technet.microsoft.com/en-us/library/cc786468(v=ws.10).aspx
Support Staff 12 Posted by Kyle Swank on 01 Sep, 2012 04:04 PM
Hi Peter,
Thanks for the +1. We'll see what we can do in the future. Again, no promises as I mentioned before. But perhaps we can look into it more.
We'll probably be looking at the password generation features as well. Though again, no timeframe on this. But do know your voice has been heard.
Please have a fantastic weekend!
Cheers!
Kyle Swank
AgileBits Support
System closed this discussion on 13 Oct, 2012 04:11 PM.