Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by support

  1. Hi Jack, Just letting you know that we released build 8071 yesterday, which will fix this issue for you. Thanks again for all your help and patience while we figured this out. Regards Click Studios
  2. Linking Hosts to Passwords

    Hi Chris, We've never come across a customer who has enabled this logging in putty, so we're not really sure if there is a fix for it. All remote sessions are logged in Passwordstate in the Auditing table, so is it necessary to have this logging enabled? If you look in the PSLauncher.ps1 file, there is the ability to attach to processes and perform keystrokes, so maybe you could do something like this to acknowledge this popup, but it might take a bit of testing to achieve. Not sure if this is a separate process though, so it might be a bit difficult. Regards Click Studios
  3. Changed to SAML2 / How to move back

    Hello, You will need to login with your Emergency Access login password, and this URL can be accessed by appending /emergency to your URL. I hope this helps. Regards Click Studios
  4. Hi Everyone, Today we have release build 8071, which includes bug fixes. Full changelog can be found here - https://www.clickstudios.com.au/passwordstate-changelog.aspx Regards Click Studios
  5. Hello, We think you should be able to modify our PowerShell script for this to work. The script can be found here - "C:\Program Files (x86)\Passwordstate Remote Session Launcher\PSLauncher.ps1". Can you try adding the line below just before the other two SendKey commands, that you see in my screenshot below. This will cause the Enter key to be clicked. [System.Windows.Forms.SendKeys]::SendWait("{ENTER}") #Send keystrokes We hope this helps. Regards Click Studios
  6. Sharing passwords with clients

    Sorry Rob, I wasn't aware that's what you were referring to. You would need to use our Allowed IP Ranges for this i.e. configure your trusted networks, and then for anything else, select a different authentication option. You can find this on the screen Administration -> Passwordstate Administration -> System Settings -> Allowed IP Ranges tab. I hope this helps. Regards Click Studios
  7. Sharing passwords with clients

    Hi Rob, The Self Destruct message is not designed to work with any Authentication options, as the recipient of the messages does not need to have an account setup in Passwordstate. We would need to completely redesign this feature if we wanted to do this. Longer term we are also considering a Cloud-Based version of this feature - maybe this could be something you can make use of as well. We haven't designed how this would work yet, or the security around it. Regards Click Studios
  8. Thanks for letting us know Brian.
  9. When trying to access the new Windows API Documentation from the Help menu in Passwordstate 8, it is possible you get a Windows based prompt asking for a username and password. To fix this, please ensure your Passwordstate URL is located in the Local Intranet Zone. To see if it is located in the Local Intranet zone, open Internet Explorer, browse to your website and open Internet Options -> Security. If it is detected it is in the Local Intranet zone, it will appear blue as per below screenshot: If you need to you can add the site in the Internet Options above, or add the site to group policy to ensure all machines detect it by default.
  10. Hi Jack, Thanks again, as we've been able to reproduce this issue now. We've made some changes and fixed most of the issues, and only have one small issue outstanding with the Password Reset Portal. So we hope to have a new build available tomorrow to fix this issue once and for all. Regards Click Studios
  11. Hi Brian, Those two buttons below should take you to each of the relevant URLs - are they taking you to a different URL?
  12. Thanks Jack - we do appreciate all your help. We've going to try and setup our own server in a different language, as we need to reproduce this issue ourselves - we don't want to keep asking for your help in testing this. Hopefully we should have some good news early next week some time. Regards Click Studios
  13. Hi Ted, Sorry you've run into this issue, and we believe this bug only affects customers who have upgraded from version 7. We will have a fix in the next release for this, but for now can you please do the following: Edit the Discovery Job, and re-select the appropriate Host Type and Operating Systems options Using SQL Server Management Studio, execute the following SQL script: DECLARE @ScriptID int SET @ScriptID = (SELECT ScriptID FROM [ValidationScripts] WHERE ValidationScripts.ScriptName = 'Validate Password for Windows Account' AND ValidationScripts.Inbuilt = 1) SELECT @ScriptID UPDATE [DiscoveryJobs] SET ValidationScriptID = @ScriptID WHERE JobType = 'Windows Local Admin Accounts' This should resolve the issue for you. Regards Click Studios
  14. Hi Brian, Is your URL being detected in the Local Intranet Zone in IE - can you share a screenshot? And can you tell us which browser you are using? If it is, then the following forum post provides a few more suggestions which will fix this - https://www.clickstudios.com.au/community/index.php?/topic/1305-passwordstate-prompts-for-authentication/ Can you let us know if any of the following helps? Regards Click Studios
  15. PS in HA in Azure (multi region)

    Hi Matt, Thanks for your post, and I'll try and provide some guidance - we do not have much in the way of experience with Azure, but hopefully between your knowledge of Azure, and ours of Passwordstate, we can get your questions answered. Passwordstate can connect to any version of SQL Server (2012 an above), and it really doesn't care what database replication technology is used. With On-Premise solutions, you can use Transnational Replication, High Availability Groups, Clustering etc. Within the web.config file, you will see the "database connection string" - it is this configuration which governs which SQL Server it can connect to. We've done limited testing with Azure SQL, and it seems to work fine - we can have Passwordstate pointed to one Azure SQL DB, and it seems to failover without any issues. So I do not believe this would be an issue for you. When you install the second node of Passwordstate, we recommend setting the PassiveNode key in the web.config file to "active", and then both Nodes of Passwordstate can have write access to the DB's - changing this key simply means the second Node will not duplicate processing with the Passwordstate Windows Service i.e. sending emails, synchronising AD Security Groups, performing Password Resets, etc. I hope this helps, and please let me know if you have any further questions about this. Regards Click Studios
  16. Thanks Jack, and this confirms what we believe the issue is. I've just sent you an email with the new test build, and hopefully this will resolve it. Thanks again for all your help. Regards Click Studios
  17. Hi Jack, Can you do me one more favour? On your version 7 install which was upgraded to V8, does this have the same time/date settings as the failed server? If so, can you go to the Preferences screen, and then 'Authentication Options' tab, and try changing the password for an account - I'd like to know if this fails at all? Thanks very much. Regards Click Studios
  18. Hi Jack, Thanks very much - we really appreciate it. This won't be today though, as we need to make the coding changes, recompile, and upload for you. I'll send you a message as soon as we have it ready. Thanks again. Regards Click Studios
  19. HI Jack, If you're willing, we could provide you a custom upgrade zip file to test i.e. overwrite all your existing files after your initially install Passwordstate. There are two fields I can make a change on here, and then hopefully we can determine what the cause is. Let me know if you're willing to do this, and have the time? Regards Click Studios
  20. Hi Jack, We must be missing something, as we cannot seem to replicate this issue. I've tried: Time and Currency Format: Both Norwegian options And setting SQL Collation to "Danish_Norwegian_CI_AS" Rebooting the server after making these changes as well, and I cannot seem to fault this. Was your web server originally installed with English United States as the language, or was this changed afterwards? I also testing with SQL being installed on the same web server - I doubt that would make any difference. Regards Click Studios
  21. New Entry Time Out

    Hi Michael, You should only be logged out if you are inactive on the site for the timeout period specified - which is 10 minutes by default. You can check this on the screen Administration -> System Settings -> Miscellaneous tab. Are you leaving the Add Password screen open for more than 10 minutes without any activity on the screen? If you are not, then do you have any Anti-virus software installed on your web server - we've seen McAfee and Trend kill sessions in IIS, and this could be the cause? Regards Click Studios
  22. Hi Jack, Thanks very much, and we'll setup a new server today with those Time and Currency Format, and see if we can work on a fix for this. We appreciate the feedback. Regards Click Studios
  23. That's very odd. All of our SQL Servers are set to a collation of 'SQL_Latin1_General_CP1_CI_AS'. I wouldn't have thought that collation is that much different to the one you selected. We'll set up a new SQL Server tomorrow with your collation, and forms based authentication, and see if we can reproduce the issue. Thanks for working with us on this. Regards Click Studios
  24. Improve Bad Passwords feature

    Thanks Nick I'd expect we'd be able to get reasonable performance as well if we only performed the check on clicking the 'Save' button, but we'd need to think about whether we want to make this change. We've had some customer's who's SQL Server times out trying to insert 10,000 records for our WordDictionary table - I wonder how it will go inserting 300 million records, with 5 GB of data