parrishk

Hi, While I can agree that this "should not need to be done all that often" it seems that is the case here. Typically, this is because of people switching phones. That is why I think it would be beneficial to be able to use the API. Writing a custom Powershell function would allow us to simply specify the user needing reset without modifying the script each time. Just a thought but if it is not on the roadmap then I will just have to use the GUI :-) Thanks for getting back to me!

It would be a great benefit to be able to resent QR codes to users via the API. Currently, have to go into each user account's settings and resend via the Email QR code button. Is this in the works?

Are you trying to access via https://passwordstate:9119 internal to your network or from the Internet? It will not work with just https://passowrdstate:9119 if not on the same network. As far as I know it should work fine when on the internal network... Can other mobile devices access it with just the name?

As Support said this looks like an issue with the IIS bindings. If the hostname you are trying to access the server with (MyPersonalPasswordState.com) is not in the list of bindings on IIS (Passwordstate01) it will throw that error. You can add the desired hostname through IIS as seen below.

Thank you GeoffO!!

Thank you for getting back to me on this. I believe we have already narrowed down the ports that were needed. Pretty sure it was everything on this list :-)

Good morning, Just checking in to see if you guys are able to provide any information on this. Thank you!

Good morning, We have actually already disabled the mobile site due to it not allowing two-factor auth. This seems a little counter-productive to me. Using the main site requires two-factor auth but appending /mobile to the end or using a mobile browser only required one form of auth...Unfortunately, this does not meet our needs so we will be keeping an eye out for what is to come with Version 8. It would be nice to have the ability to place Passwordstate in the DMZ just for web access and keep the production server in the internal network. There are many instances where we are unable to access our internal passwordstate server when we are connected to client VPN's. Thank you for the feedback.

Hello, The only reason we have moved it to the DMZ was to access it from the Internet. I heard about the mobile client but assumed it was for mobile devices. Will this work for normal devices too? Does the mobile site need to be enabled for this to work? We have decided not to enable the "mobile site" at this time because we want to be able to utilize dual-factor authentication. Currently, it looks that it only requires one form of auth. If this mobile client can be used for this purpose that would be excellent!

If we were to place Passwordstate in the DMZ for accessing via the Internet could we also have an installation on our internal network to utilize host scanning and password discovery features without needing a second/site license?

Hello, Do you have a list of required ports for Passwordstate to communicate with Active Directory, SQL, Etc.? We have moved our Passwordstate server to our DMZ and have had a fun time trying to find all of the ports that it is trying to use. I can't find anything in the documentation. THanks!

Suppose you had a CSV with two columns, one titled "Title" and the other "Password". This is what your Powershell script would look like. $tokenfile = "C:\users\myuser\tokens.csv" $tokens = import-csv $tokenfile foreach ($token in $tokens){ # Powershell Request (POST) $password = @{ PasswordListID="654654" #change to appropriate list ID Title = "$($token.title)" Password = "$($token.password)" } $passwordjson = $password | ConvertTo-Json $result = Invoke-Restmethod -Method Post -Uri https://passwordstate:9119/api/passwords -ContentType "application/json" -header @{ "APIKey" = "apikeygoeshere"} -Body $passwordjson }

You may be able to utilize the API and Powershell to grammatically create the passwords in the list. You can create a CSV with the 50 tokens and have Powershell do a "foreach" loop that will POST the new password item to the list. I used it when we did our initial import to Passwordstate and thought the process was actually pretty simple once playing around with it for a little bit.

By "strong authentication" do you mean two-factor?

I agree, this feature would be beneficial to us as well. We don't use the documents option very often because they aren't always the easiest to find/spot unless you know where to look.