Jump to content

Chrome Extension Not Saving Information


Recommended Posts

Hi bluegamma,

 

We've seen this a couple of times during testing the extension, and generally it means there is some sort of issue communicating with the Passwordstate API. Are you able to reboot your Passwordstate web server to see if this fixes it? If not, how about restarting IIS?

 

If none of these suggestions work, are the graphs in Passwordstate working, and the Password Generator in the toolbar at the top of the screen - both of these make calls to the API. If these things aren't working, can you bring up the JavaScript console in Chrome, and see what errors it is reporting.

 

Let us know what you find.

 

Regards

Click Studios

Link to post
Share on other sites

We're having the same issue, two different users (one of them is me).

 

We had not used the extension before the upgrade to 7086.

 

API is working (password generator, graphs, and we use the API for other stuff too).  Rebooted the machine hosting passwordstate, disabled/enabled the extension.

 

The developer tools window closes once you click save so I can't see if there are any js errors.

 

In the IIS logs I'm not seeing any calls to the API other than "/highavailability/GetPrimaryStatus", "/searchpasswords/" and "/generatepassword", no matter how many times I click save.

Link to post
Share on other sites

Hi bpinson,

 

Within Passwordstate, and on the Preferences screen, can you confirm that you saved the API Key - we've had a couple of customers who forgot to hit the save button, but I seriously doubt this is your issue.

 

To help troubleshoot this further, can you do the following for me:

 

  • Download Fiddler from here, and install it on your desktop - http://www.telerik.com/fiddler
  • As per the attached screenshot below, can you test the initial authentication - you should receive a HTTP Response 200, with a auth_key value. The setting you need to configure in Fiddler are:
    • POST verb
    • The url of https://yourpasswordstateurl/api/browser/authenticate
    • Add the Content-Type of Content-Type: application/json
    • In the request body, specify in the format of {"UserID":"halox\\msand","APIKey":"bbbd8b94fa2356629837c53ba4fde28","BuildNo":"7086"} - if using a domain account, you must parse double \\ when using Fiddler

post-1-0-01583300-1419891100_thumb.png

 

Can you let me know what happens when you do this?

 

Regards

Click Studios

Link to post
Share on other sites

Thanks bpinson. We considered also performing the Save when you hit the Generate button, as a few customers have done this now, but if the user wanted to cancel out of the screen after hitting the generate button, then the API Key would be different to what they're expecting. Maybe we could look at reporting back in the Chrome extension that the API Key doesn't exist - I think this would be the best option.

 

Regards

Click Studios

Link to post
Share on other sites

Hi Adrian,

 

The URL needs to be whatever you currently use for accessing the site - so yes, normally https. It would be something like https://yourpasswordstateURL or https://yourpasswordstateURL:PortNumber - if you are using a non-standard port number.

 

And the AD account must be specified in the format of domain\username

 

Regards

Click Studios

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...