• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs
Advanced

Not what you are looking for? Ask the experts!

This forum thread needs a solution.
Kudos1 Stats

IdentiySafe will not allow simalr url logins to be created.

I get this error box when I am trying to add a second url that is similar but does have some text that is different.

https://socen.smarthub.coop/Login.html#login:

https://garkaneenergy.smarthub.coop/Login.html#login:

any help would be appreciated.

Replies

Kudos1 Stats

Re: IdentiySafe will not allow simalr url logins to be created.

I have this same problem with subdomains for the same high-level company domain. For instance, many vendors separate their Support webpages from their Shopping webpages in this way:

buy.bigcompany.com/logon.htm

support.bigcompany.com/logon.htm

I can save the same userid & password to the vault, when they are initially captured by Identity Safe, when creating both the Buy account and the Support Account.

But woe unto you, if you try to edit either of those entries - even for something simple like adding a Tag to the Vault Entry. The Big Warning shown above by jsorejgs, will block any attempt to edit either the "buy subdomain" logon or the "support subdomain" logon, because they are using the same Userid for 'bigcompany.com'.

Can we please have a way of overriding this WARNING? Perhaps an 'ignore' button on the dialog box?  If the logon credentials were good enough to store initially, they should be good enough to edit later on. Because it's obvious that Identity Safe can't distinguish between the two subdomain URLs for the same bigcompany.com.

Kudos0

Re: IdentiySafe will not allow simalr url logins to be created.

Hi,

Not sure this will work, but have you tried to change the user name of one of the log-ins?  I sometimes use yank and yank2.  I have not specifically tried it with ID safe, but it works on some sites that claim "the user name already exists" when I first register for the site.

Also I have seen a similar "block error" occurring when you try to edit the Title of a log-in: "Login Name already exists"

Kudos0

Re: IdentiySafe will not allow simalr url logins to be created.

Hello Yank,

Yes of course, having an alternate username would avoid the problem. However, for the example I provided, the Username MUST BE an email address. This is the case quite often, as I'm sure you know.

I would prefer ALL my account communications with 'bigcompany.com' be sent to the SAME email address, rather than to separate email addresses for Shopping or Support. I can always modify the Title to be something unique like 'BigCompany - Sales' and 'BigCompany - Support'. 

The WARNING about duplicate usernames (email addresses) is caused by a failure to recognize the unqiueness of the subdomain URL, which is used by BigCompany to separate Sales and Support and Forums.

Norton itself does this. For instance:

community.norton.com

login.norton.com

support.norton.com

buy.symantec.com/estore/

I hope this clarifies the situation.

Kudos0

Re: IdentiySafe will not allow simalr url logins to be created.

It is possible to get Norton to take a look at this situation.  Navigate to the URL, click on Vault is open and then select Options from the Current Site block at the top of the drop down.  The select Report an issue with this site.  A new page will open with the URL already entered and you can then explain what is happening and hopefully Norton can advise.

I know that is not much help, but it is all we can do in this case, as e are customers the same as you are.

Kudos0

Re: IdentiySafe will not allow simalr url logins to be created.

I agree with wanting to have a cancel on this warning.  In my example the subdomain names are the same but they are logins pages for two different utility companies that use the email as the username. If I change one of the user name emails to something different I get the option to pick which one I want to use and of course one of them will not work.

I will report this to Norton.

Kudos0

Re: IdentiySafe will not allow simalr url logins to be created.

I did report this asking for an override on the popup message or better string comparisons on the url's in question.  Thanks for pointing me to the feedback location.

Kudos0

Re: IdentiySafe will not allow simalr url logins to be created.

jsorejgs:

I did report this asking for an override on the popup message or better string comparisons on the url's in question.  Thanks for pointing me to the feedback location.

Please share your answer when you get it.

Kudos0

Re: IdentiySafe will not allow simalr url logins to be created.

Yup - This definitely is now another bug in the current IDSafe   (but it didn't used to be) ... Seems as though Norton suddenly has never heard of subdomains - But FWIW this used to work just fine in earlier versions of IDSafe, so why the grand improvement Norton? 

Kudos0

Re: IdentiySafe will not allow simalr url logins to be created.

I received this answer from FWIW.

FWIW...

The Title field is used as the IDSafe internal filing operator field.  It can be set (and/or changed) to anything you'd like it to be (just so long as it is unique and doesn't conflict with another already saved entry record).  This can be done without affecting (changing) the Username field which (in this case) contains your non-unique email address which you've pointed out is expected by the other various sub-domains off the primary domain...

The problem occurs (actually is exacerbated by) the IDSafe's habit of auto-assigning/applying the Username field also to (and as) its internal record filing/keeping ID field, aka the "Title" field.

Bottom line, you can edit the memorized sub-domain login records and change the Title field (only) to something else that's unique and your conflict issue should go away...

This did not work. I am  using unique Title Names.  Any other suggestions? Try adding my two examples from my first post.

Kudos0

Re: IdentiySafe will not allow simalr url logins to be created.

I have been playing around and digging a bit deeper into this "smart hub" login and it appears this is something that you get directed to from the company (utility) you are trying to get to and then you have to  login to the "smart hub".

It appears to me that they might have got caught with their pants down in that 2 different companies in the same general area are using the smart hub servers for their log in verification.  Thus even though they come up with different utilities names - you are in fact logging into the same URL being used for the log-in - thus it shows as the same URL.

Please excuse me as this is not an area of my expertise (far from it) but hopefully someone will be able to understand what I am getting at in regards to logging in to the same "smart Hub location" - even though they are different companies/utilities.   In other words, you are logging into the same "smarthub.coop/Login.html#".  Hopefully that makes sense to someone!

Thanks - I just spotted your PM - I was wondering where the FWIW came from - I understand that is the response from Norton - correct?

Kudos0

Re: IdentiySafe will not allow simalr url logins to be created.

Hi jsorejgs,

Not to get you wrong -  what is the problem you are trying to solve by adding same user name for both the URLs? If that's for IDSafe auto-fill, you need not add a new login for that second domain with the same user name. It would automatically get filled in for both the URLs with one login being added in the vault.

Because of this reason - you will not be allowed to create a new login with same user name(one similar to already existing) for the same domain. Let us know if you need any help further.

Regards,

Prasanna

Kudos1 Stats

Re: IdentiySafe will not allow simalr url logins to be created.

I am trying to add two separate logins to two separate different urls, They do have the same sub domain but go to two separate login pages for their each respective home page. They both require my email ( I only use and have one ) as the user name.  Please relook at my concern.  Thanks

Kudos0

Re: IdentiySafe will not allow simalr url logins to be created.

... If that's for IDSafe auto-fill, you need not add a new login for that second domain with the same user name. It would automatically get filled in for both the URLs with one login being added in the vault.

Because of this reason - you will not be allowed to create a new login with same user name(one similar to already existing) for the same domain. Let us know if you need any help further. ...

Hi Prasanna,

So what does one do if a different (unique) login PW is required for each of these URLs?  FYI, Besides the other URL subdomain examples already given, such is also the issue when trying to deal with the current IDSafe interface to create logins for many of California's .ca.gov sub-domain based websites...

Kindest regards,

John

This thread is closed from further comment. Please visit the forum to start a new thread.