Just upgraded to NIS2012 and identity safe has gone crazy.
It used to be URL specific (to a degree) so
example.com/customerlogin
example.com/adminlogin
would store two different entries (which makes sense).
as would subdomain1.example.com/login and subdomain2.example.com/login
Now it stores everything under just the domain (example.com)
That's iritating for some people but as a developer using localhost it means a nightmare for me - each site now has a huge list of potential login usernames.
If you try to add the login manually it fails, so if you have:
Yay someone else has the same problem! just need another 20,000 people to moan and maybe they'll pull their finger out.
It used to be fine in NIS 2011, I wish I could downgrade.
They know it's a problem as their live support spent about 2 hrs on my pc trying to fix it and it even got escalated to a senior tech.
Well, the first step is admit there is a problem, but can we please have an idea of timescales otherwise I'm going to disable it and buy roboform or something because identity safe is currently a pointless feature for me.
"We are aware of this issue, and it will be addressed in a future product version or update."
That is about as much of a 'when' response as you can expect. I don't know how complex the fix is nor do I know what else it might break if applied without proper testing. The Norton staff is very careful with dates. They would rather have it done and released that have to make apologies for missing a target which proved to move faster than their repairs.
Hang in and hnag on. It will come when it gets here. Til then
As a developer of software, albeit not PC software, that change should take a maximum (and I'm being extravagant here) of 30 minutes. Add in testing of another 30 minutes. But, add in the SOX laws and we're looking at 3 days ;)
Looks like I'll be totally missing out NIS2012 then. Identity safe is a big bonus for me and I don't want it messing around like this. Looking around, Identity Safe seems to be the most reported item.
What concerns me is that if they haven't tested this bit properly what else isn't working?
I used to be quite content with norton having used it for 5+ years but I'm a little concerned now - this shows to me that little thought, planning or testing went into this.
I can only assume it is a module that is separate from the main core product and probably a junior programmer wrote it or a junior analyst spec'd it (we all have to start somewhere).
That being the case please get senior people on it now, re-write and get it released and learn from the mistakes. As a customer I expect it to be a fix, NOT wait for a new product version.
this **bleep** identity safe is also autofilling all sorts of fields - on our merchant account website it prefilled a field labelled "batch no" with my email address ? wtf?
come on guys - stop writing new stuff and get the old stuff working properly please.