support

Hi Yes, This is only an email notification. You can also ensure no users login by enabling maintenance mode, and that will give them a page explaining they cannot use Passwordstate at the moment. Certainly not what you've asked for though. Regards Click Studios

Hello, Thanks for your request. Whilst not automated like you would like, you can send 'Outage Notifications' to all users from the screen Administration -> Backups and Upgrades. Just click on the 'Send Outage Notification' button, and adjust the details as appropriate. Regards Click Studios

Hi Guys, We're also looking into a possibly bug here as well, and we'll post back once we have some more information. Regards Click Studios

Thanks for confirming We'll prioritize this for you if we have enough interest from the community - this is the only fair way we can think of for adding one feature request over another, as we have plenty to work through Thanks very much. Regards Click Studios

Hi Folke, Thanks for the feedback. With these suggestions, can you confirm you're wanting to make changes to existing Password Lists and Folders? We haven't really had much in the way of interest in doing this via the API, whereas the creation via the API is used by many customers. Do you also need this just for the initial data migration, or ongoing? We only ask because we have many feature requests we're working through, and it might be some time before we're able to work on it. Regards Click Studios

Hello Everyone, So we can prioritize all the wonderful feature requests we receive from our customers, can you please vote on any feature requests listed in this forum which are important to you. Simply reply to the thread with a +1 as your response, and this will greatly help us. Please also only vote one person per customer. Thanks Click Studios

Hello, Yes, you can do something like this, as per the example below in PowerShell. Are you also aware of the GeneratePassword option when updating passwords via the UI as well? This will generate a new password for you, based on the selected Password Generator assigned to the Password List, and then you wouldn't need to change the Expiry Date or Schedule as per below? With this example below, or if you used the GenerarePassword option, the reset would be picked up within the next minutes and processed. $NewExpiryDate = (get-date).AddDays(-1).ToString("yyyy-MM-dd") $NewSchedule = (get-date).AddMinutes(1).ToString("hh:mm") $jsonData = ' { "PasswordID":"57783", "ExpiryDate":"' + $NewExpiryDate + '", "PasswordResetSchedule":"' + $NewSchedule + '" } ' $PasswordstateUrl = 'https://myurl/api/passwords' $result = Invoke-Restmethod -Method Put -Uri $PasswordstateUrl -ContentType "application/json" -Body $jsonData -UseDefaultCredentials Write-Output $result Regards Click Studios

Hello Pferree, We do not have a Recycle Bin for Password Lists at this stage. The user is prompted twice to confirm the do wish to delete the list, so hopefully no-one will do this by accident. Regards Click Studios

Thanks Mark - we're definitely going to be working on this, and are documenting the new features we want next week. It will take a while to achieve though, as all browser extensions need to be updated - unfortunately there's not a lot of standards between all the browsers. Regards Click Studios

When browsing to your Passwordstate website, you may see a couple of different types of errors which are stopping you from accessing the website. This post will help you resolve these issues. First Issue: When first installing Passwordstate, by default the URL it chooses during the install will be the name of your web server, with a port number of 9119. These values can be changed but this post will assume you have left the default values during the install. If you enter the URL without appending the port you will see this message: The correct way to append the port is to enter it like this, and if you have the correct URL and Port your site should then load successfully: To check your URL and Port Number, open IIS on your web server, and go to Bindings. In the example below, the exact URL you should enter into your browser should be https://win2k16installs:9119 To make an easier URL to type in and remember, you can set the Port in IIS as 443, as this is the standard Port that HTTPS traffic communicates on. If you do not append a port to your URL, your web browser is smart enough to know that your site is configured with 443. If you change the port, you should restart the website in IIS and then try to access the site again. Here's some screenshots to show how this works: If you wanted to change the URL to something more friendly, like https://passwordstate, please see this forum post which will guide you through the process: https://www.clickstudios.com.au/community/index.php?/topic/1465-changing-the-passwordstate-url/ To conclude this post: For basic quick access to your Passwordstate website, you should set your bindings to be the DNS name of your web server, and if you have set a port for the site to anything else other than 443, then you should append that number to your URL in your browser. Hope this helps and if you still have issues, please contact Click Studios on support@clickstudios.com.au Regards, Support.

Hi Guys, We are documenting the next round of features for the browser extensions, and we will include this. Darly B, I was posting this information as a work around until we can develop the features you're requesting. Regards Click Studios

Thanks

Hey Greg and Daryl B, We're looking into you feature request for you, but can you confirm if you have the following settings for us: You only specify the Base URL field on the password record - screenshot 1 below On the browser form fields tab, are the login field names specified? If using our extension to save the logins, then hopefully it detected them okay - second screenshot below And in the 3rd screenshot below, this setting will not attempt to form fill any fields in the fields on the 'Browser Form Fields' tab are empty These seems to work for us, and will not form fill fields once inside your web application, but the only exception to this would be if the fields names inside the application are named exactly the same as the login screen - I hope that makes sense? Regards Click Studios

Hi Stuart, Thanks for your suggestion - we really appreciate it. We do have many feature requests that we're currently working our way through at the moment, but if we receive interest from the community on this request, then we will look at prioritising it for you. Regards Click Studios

Thanks for your request Daryl. We'll let everyone know once we've found the time to work on this, and thanks for your patience till then. Regards Click Studios

Thanks for your request Fabian - we appreciate it. Regards Click Studios

Thanks very much Philipp for your suggestion - we will look into it in a future release, and report back here when complete. Regards Click Studios

Thanks for the vote Greg. We'll consider this request when we next work on feature development for our extensions. Regards Click Studios

Hi Frank, Thanks for your suggestion - we appreciate it. If there are duplicate accounts for a sight, the extension icon should turn yellow for you, and the you can click on it to select which account you want to use to login. Regards Click Studios

Hi Alexey, No specific reason - I guess because we had a KB Article section in there, and the Security Admin manual maps to each of the menu in the Admin area. Maybe we should put in both, and probably under the Backups and Upgrades section in the Security Admins manual. Regards Click Studios

Hi Guys, Under the Help Menu, in User Manual, we have various Disaster Recovery processes covered under the KB Article section - this might help as well. Regards Click Studios

It's odd that the order of the installs can break things, but at at least it's a relatively easy fix

Hi Geoff, Thanks for your request and we'll see if we can come up with something for this. The main design issue I think we'll have is that we don't want one popup window on top of another i.e. Add Host screen on top of Add Password screen. Possibly we could just add the Host if not found based on what you type into the textbox, but there may be certain fields that need changing for the Host i.e. Operating System. We'll have a think for what's possible here. Regards Click Studios

Hello Achim, Thanks for your feature request and interest in our software. Unfortunately we do not have any language translation at this time. It is something we would like to work on, but it’s an incredible amount of work to change all pages in Passwordstate, in addition to the translation files themselves – and we rarely get requests for this. We do have many customers throughout Europe in different languages using our software, so we do hope you can still make use of our software without the language translation. Regards Click Studios

Issue: We've had a few reports of customers who have not been able to sync AD Security Groups, or possibly not able to add users into the system from Active Directory. Symptoms: Some symptoms you may see is when adding in a AD Security Group, it will not enumerate the members. Or possibly you might be presented with a Error page in Passwordstate saying it cannot query Active Directory. Possible Cause: By default, Passwordstate only requires an account that has "Domain User" privileges in AD to be able to sync objects, however if you have hardened Active Directory to minimize the visibility of containers for certain users, you may need to elevate the permissions for your Privileged Account. How to Test: As a temporary test, add your Passwordstate Privileged Account to the "Domain Administrators" security group in Active Directory. If this resolves the issue, then this indicates it's a permission issue. How to Fix: Unfortunately every AD environment that has been hardened can be different, so it's difficult to say exactly where the issue lies. Normally when companies harden AD they may remove the ability for the "Authenticated Users" on certain containers to hide them, but some applications built with standard .NET code can have issues with this, including some of Microsoft's. We would suggest you check permissions for each container starting with Users and Computers, and confirm whether or not the Authenticated Users has read access, as per below screenshot: Next, you should check any other container that you have computers or user accounts stored in for the same permissions above, and this will include and nested containers, as the problem may be caused at any level. Finally check the top level domain and then depending on the results, you can do one of a few things: Restore the default AD permissions to allow Authenticated users to have read access to all containers where you have users or computers, and also ensure the permissions filter down to all nested objects - We realize this may not be possible. Give your Privileged Account Read access on all containers, and ensure permissions filter down to all nested objects Elevate the permissions of your Privileged Account to one of the built in AD Security Groups. Suggestions are: Account Operators, Administrators, Domain Administrators or Pre-Windows 2000 Compatible Access More Information: You may possibly run into the same sort of issues in Passwordstate, when attempting to let Passwordstate reset a password for an Account in AD. For most accounts in a domain, the privileged account Passwordstate uses should only need to be a member of “Account Operators” built in security group to be able to reset the passwords. However, this won’t allow the account to reset passwords for higher privileged accounts like Domain Administrators, or Enterprise Administrators. To reset passwords for accounts like these, the privileged account must also be a member of one of the Administrator Groups, either “Administrators” or “Domain Administrators”. This is by design from Microsoft, because if you can reset a domain Administrator password, then you effectively can use that account to perform domain admin tasks, so why not just make it a member of the Domain Admins in the first place? There are ways to set granular password reset permissions on account attributes, which will allow an account with less privileges to reset a domain admin password. We would not like to provide advice on this though as you can imagine it could be different for every domain. So summary, your privileged account should be a member of "Account Operators" group for all normal password resets, or “Administrators” to reset passwords for any Administrator type account. To mitigate against the risk of having these high privileges for your account, you can configure your privileged account to reset its own password on a regular basis in Passwordstate. Just link it to a password record from within the Privileged account screen, and set it to reset as often as you like. If you still find you cannot perform sync's/ resets, please contact Click Studios on support@clickstudios.com.au and if we have any more current information about this, we will let you know. Regards, Support.