Jump to content

support

Administrators
  • Posts

    5,076
  • Joined

  • Last visited

  • Days Won

    317

Everything posted by support

  1. Issue: If you want to do some quick testing of a Password Reset Script for troubleshooting purposes, this can be achieved if you are a Security Administrator, and have access to the Administration -> Powershell Scripts page. This guide also applies to testing Account Discoveries and Account Heartbeats. Process: As a Security Administrator, open the page below and choose Password Resets: Find the script you want to test, and select Test Manually form the Actions Menu: Enter the appropriate details for the script, and when executing it you should either see a "Success" message, or an Error message like this screenshot below: If you want to adjust the script in any way, like commenting out all the custom errors so you can get the exact error message back from Powershell, you can modify the contents of the script like this screenshot below, and re-run the script again. If you need to, send a screenshot of the results to Click Studios support and we will do our best to help troubleshoot the issue. Regards, Support
  2. Hello Andy, Unfortunately we do not have a feature for that - we can only discover Local Administrator accounts within Local Admin Groups. For domain accounts, we generally recommend our Active Directory Accounts discovery job instead - which can query domain OU's or Security Groups. Regards Click Studios
  3. Hi Mike. Unfortunately it's not currently possible, but you can vote on the following feature request for this - https://forums.clickstudios.com.au/topic/14887-list-documents-from-api/ Regards Click Studios
  4. Passwordstate has browser extensions for Chrome Firefox and Edge, and should also work in any other Chromium based browser. Below are a few tips for using these browser extensions: Field IDs On your password records that you have saved for 3rd party websites, you'll find a tab called field IDs. If these fields are blank, the the browser extensions will try to guess the fields to insert the username and password into when auto-filling your credentials: Auto-filling into Wrong Fields If you find that the browser extensions appear to be auto-filling credentials into incorrect fields, when logged into the website, this can be fixed by setting the correct field IDs on your password record. This blog post explains ho you can use a built in tool within the Browser Extensions for this: https://blog.clickstudios.com.au/example-mapping-field-ids/ Searching in the Browser Extensions When searching within the browser extensions, you can search for the Title, Username or URL to find the correct record. Password records without a URL will not be shown in the search results. This is by design and it due to the nature of the Passwordstate software. Being an enterprise Password manager, it's possible to store tens of thousands of passwords for your network, and showing all of these in the extension would make it difficult to use. The browser extensions are designed to save and auto-fill website credentials, and therefore they will exclude any record that does not have a URL attached. Ignored URLs If you find the extensions are not automatically filling in your credentials, it's possible you have the website set as an ignored URL. This blog post explains this in great detail: https://blog.clickstudios.com.au/browser-extensions-options-when-saving-and-ignored-urls/ Regards, Support
  5. Hello, Please try the following format: $PasswordstateUrl = 'https://password.server.com/winapi/passwords/' + $pwid +'?MoveToRecycleBin=False' Invoke-Restmethod -Method Delete -Uri $PasswordstateUrl -UseDefaultCredentials Regards Click Studios
  6. Hi Carlo, Thanks for the vote, and suggestions. Looking at each of those solutions, unfortunately they do not appear (at an initial glance), to be appropriate for an Enterprise solution like ours - they seem client based. If there is a solution available, we would need: To be able to specify which users are recorded Prevent the users from turning off the recording i.e. uninstalling a browser extension Have the recordings sent to a network share, so they can be replayed back from the UI in Passwordstate Regards Click Studios
  7. Hello mathijs, When clicking this button, we do a postback to the server to perform the following: Check your account has access to the password record Retrieve the password Add auditing data When we postback, the whole ASP.NET Viewstate payload is sent back to the server, which includes data for all controls on the screen. So the more rows in the grid, the larger the payload to send back to the web server. I've just tested a grid which is showing 30 records, and the timing is around 350ms for me. So if you are seeing poor performance in your environment, we recommend reducing the number of rows in the grid, and use the search functionality instead - to find the records you need. Regards Click Studios
  8. Hello Mathijs, With that video you linked to, it is not taking more than 1 second - as soon as you see the Clear Clipboard button appear, the contents is in the clipboard. We have optimized this updated feature as much as we can, and we will not compromise on security and revert back to the older client side method. If you are seeing performance issues, then please see this forum post for suggestions - https://forums.clickstudios.com.au/topic/15217-delayed-copy-button-action-when-upgrading-to-9653. In our environments, the process takes approximately 300ms. Regards Click Studios
  9. If you are running Passwordstate version 9, and if you need to rebuild the web.config file from a backup, take a copy of the C:\inetpub\Passwordstate\setup\scripts\master_files\web.config.install file, and replace the following data below: 1. SQL Server name, Instance and Port if appropriate. Examples of this are webserver03, webserver03\sqlexpress, webserver03,1495. If using the default instance of MSSQLServer, or the default port of 1433, appending the instance or port is not necessary 2. The database name, typically passwordstate 3. SQL username, typically passwordstate_user 4. SQL user password (match what current password is in SQL, reset in SQL if required to match what is int he web.config file) 5. Setup Stage should always be "Setup Complete" 6. Secret 1 and Secret 2 Now replace the existing c:\inetpub\passwordstate\web.config file with this rebuilt one, and you should be able to access Passwordstate again. Regards, Support
  10. Hello JSmith, Just letting you know we've finished this feature request, and will be available in the next release - in about 1 to 2 weeks time. You will be able to use the same PreventAuditing parameter. Regards Click Studios
  11. Thanks for your kind feedback - we really appreciate it. Have a great day. Regards Click Studios
  12. Hi Guys, We've finished this feature, and it will be available in the next build - about 1 to 2 weeks time. Regards Click Studios
  13. Hi Digital Dynamics, Are you able to log the support call to our team via this page, and we'll assist to get this working: https://www.clickstudios.com.au/support.aspx Regards, Support
  14. Issue: Passwordstate backups not running on the schedule you have configured under Administration -> Backups -> Settings page. Whilst troubleshooting this issue, can can take a quick manual backup of Passwordstate at any point in time by following this guide: https://forums.clickstudios.com.au/topic/13911-manual-backup-using-sql-management-studio-tools/ Troubleshooting Step #1 Log into Passwordstate and go to Administration -> Backups -> Settings page and click the Test Permissions Button. If you see any errors on this page this may help you understand that the issue is. ie it may have trouble writing to the network share, or it may have trouble backing up the database. Troubleshooting Step #2 Log into your Passwordstate webserver, and check if the Passwordstate Windows service is running. If it isn't, start it and wait for next schedule backup to occur and confirm it has backed up all files to disk. Troubleshooting Step #3 Are you using the High Availability Version of Passwordstate, where you have 2 x Passwordstate websites running in sync? If you are, go to Administration -> Authorized Web Servers and confirm you have at least one server on this page that has the Server Role set to "Primary Server". If you need to make a change on this page, restart the Passwordstate Windows Service on both of your Passwordstate web servers. It actually cannot hurt to restart the services regardless at this point, and restarting services is non-disruptive for your end users. Troubleshooting Step #4 On your web server, are there any errors in the Application Event Logs in Event Viewer, relating to the Passwordstate Windows Service? If there are, screenshot them and send them throgh to Click Studios Support to analyze, and mention in the support call your scheduled backups are not working. To log a support call with Click Studios, please do so via this page: https://www.clickstudios.com.au/support.aspx Troubleshooting Step #5 Do you have your Windows Service running under the identity of a custom Active Directory Account? If you do, please set it back to the default built in account called "Local System" and restart the service. Wait for next scheduled backup to execute and check if this has fixed the issue. If you still have issues running backups, please download and run the Powershell script in this forum post on your Passwordstate web server, and send Click Studios Support the results? https://forums.clickstudios.com.au/topic/2518-passwordstate-support-information-script/ Regards, Support.
  15. Dear customer, We’ve noticed that no one has answered the forum post yet from the community – You are more than welcome to log this with Click Studios Support via this page if you like: https://www.clickstudios.com.au/support.aspx Regards, Click Studios Support
  16. Issue: Customer has noticed that emails are not being sent anymore when they previously used to work. Things like scheduled reports or notifications about system event etc. Recommendation: Before doing any of these steps, go to Passwordstate Administration Home, and click on View Queued Emails. Purge any emails on this page. When you fix this issue, any emails on this page will all be sent out at the same time, which could potentially flood inboxes and send users old emails that are no longer relevant. Troubleshooting Tips: Option #1: Go to Administration -> System Settings -> Email, Proxy & Syslog Servers and click the Test Email button where you have your email server details. This should send an email to your inbox. If it does, this will mean there is an issue with the Passwordstate Windows Service. If it doesn't, it should error indicating your email settings are incorrect on this page. Option #2 Check the Passwordstate Windows Service is running on your web server and start it if it is in a stopped state. This should fix the issue. Option #3 Check Application Event Logs on the web server for any exceptions related to the Passwordstate Windows Service. Forward these onto Click Studios support for analysis: https://www.clickstudios.com.au/support.aspx Option #4 If you suspect that some users are getting emails but others aren't, check the user has a valid email address assigned to their name under Administration -> User Accounts Option #5 You should always have at least one server with the role of "Primary Server" under Administration -> Authorized Web Servers. Having the Primary server role means the Windows Service is fully functional on that server. If you have made a change to these roles recently, or need to set one to be a Primary Server now, make sure you restart the Passwordstate Windows Service again to pick up this change. Option #6 Under Administration -> Auditing, filter on the Activity Type of 'Email Sent'. If you can see recent activity of emails being sent on this page, that means the emails have been sent out from Passwordstate, and possibly they are getting caught in a spam filter. Option #7 Check Administration -> Error Console for any errors relating to emails being sent. These errors are returned form your email server, and googling them should help resolve email server settings within Passwordstate, or perhaps they can help adjust your email server to allow a 3rd party application to send out email from it. Regards, Support
  17. This guide will show you how to find some critical details about your Passwordstate website. Step 1: Log into Passwordstate as a Security Administrator, and confirm your webserver name. This is where you have Passwordstate installed. Step 2: Log into your web server, and open IIS (Internet Information Services). You can search for this on the Start Menu. Once open, select your Passwordstate website and click Bindings. Then select your HTTPS binding and click the Edit button. A window will open showing the Hostname, Port number and the SSL Certificate being used as per the screenshot below. If you view the certificate on this page, you can see detailed information about the certificate such as when it will expire, and you can export the certificate from this screen, if required. If using Port 443 which is the default port that comes installed with Passwordstate, you do not need to append it to your URL when typing it into your browser. If using any other port, you will need to append the port on the end of the URL. In the example above, the URL would be https://passwordstate.clickdemo.com Regards, Support
  18. Dear customer, We’ve noticed that no one has answered the forum post yet from the community – You are more than welcome to log this with Click Studios Support via this page if you like: https://www.clickstudios.com.au/support.aspx Regards, Click Studios Support
  19. Issue: You attempt to log into Passwordstate, but you get the following error: Potential Fixes: This error can be caused by a few different options, and below we will list these to help you investigate the issue Web.config file explanation: On your Passwordstate web server, you will find a c:\inetpub\passwordstate\web.config file. You should see a connection string which includes four pieces of information - your database server and instance, database name and a SQL username and password. An example of this can be found below: If you cannot find these details in your web.config file, then this will mean someone he encrypted the file for added security, and you'll need to decrypt the file to be able to read it in clear text. More about what an encrypted file looks like, and how to decrypt it can be found in this forum post: https://forums.clickstudios.com.au/topic/2699-encrypting-and-decrypting-the-webconfig-file/ Potential Fix #1 First thing to check is that the password for your SQL account in your web.config file is valid. Using SQL Management Studio Tools, try establishing a connection to your database server using the detail from your connection string. If the connection is refused, you will need to update the password in the web.config file to match the actual password on the database server. Potential Fix #2 If your database resides on a separate server, check to see if there are any firewalls blocking access. To test this, open Powershell on your web server, and run the following command, but substitute in your database server name: Test-NetConnection -ComputerName SQLServer01.clickdemo.com -Port 1433 If this does not come back with a true result, it could mean that either a firewall is blocking access, or your SQL server is listening on a different port than the default port 1433. To check if you are using a differnt port, open SQL Server Configuration Manager on your database server, and look for the TCP/IP connection properties. You will see the Port number under the IP Addresses tab: If you find that the port is different, you will need to update it in your web.config file, using this example below as a guide: Potential Fix #3 Sometimes we have seen the SQL account password has expired. Log into your database server using another privileged account, and deselect the password policy for the "passwordstate_user" account (this is the default account most people will use) Potential Fix #4 Check for outstanding Windows updates that require a reboot on both your web server, and database server (assuming the database is hosted separately). Just search for updates from the Start Menu and if a reboot is required, schedule one as soon as possible. Potential Fix #5 If you are using SQL Replication in any capacity to replicate data between two database servers, you may be using a SQL Listener. A SQL Listener is a virtual computer in Active Directory, that makes connections to either of your databases where you are replicating data to. If you are using a SQL Listener, try hardcoding the database server and and instance in the Connection String, in the web.config file. Potential Fix #6 Check that the SQL Services are running on your database server: If you still have connection issues, please log a support call with Click Studios Support: https://www.clickstudios.com.au/support.aspx Regards, Support
  20. Issue: You have installed Passwordstate on Server 2022, and are attempting to run through the initial set up wizard. Your Test Connection button comes back as a successful test, but half way through the wizard the screen crashes asking you to look in the "DebugInfo" table for any error. You check the DebugInfo table, and nothing gets returned. Potential Cause: At the time of writing this forum post we've only seen this issue a couple of times, and we believe this occurs if TLS 1.2 has been disabled on the web server. This could be applied via Group Policy or may be built into the OS by default. TLS 1.2 is still perfectly safe to use, and TLS 1.3 will be supported by Click Studios we think in the next major build we release. Potential Fix: Enable TLS 1.2 on your system, reboot, and reset the initial Passwordstate set up wizard. The easiest way to do this is with IIS Crypto tools, and this process is outlined below: Download IIS Crypto GUI from this link on your web server, and open it once downloaded: https://www.nartac.com/Products/IISCrypto/Download Click the Best Practices button Reboot your web server Reset the Passwordstate installer as per these instructions: https://forums.clickstudios.com.au/topic/1663-resetting-the-passwordstate-setup-process/ Run though the initial set up wizard If for some reason this does not help, please log a support call with Click Studios Support: https://www.clickstudios.com.au/support.aspx Regards, Support
  21. Hello Mark, We need to update the wording on this screen, as it has not been done since we've added the App Server feature. The message is referring to the 'Primary Server' Server Role, you see on this screen. So there are no issues with you deleting the App Server role here. Regards Click Studios
  22. Hello Roman, Unfortunately there are no plans to develop extensions for those browsers. We use to have Safari extensions, but then Apple made large architectural changes to how Safari extensions work, requiring software developers to completely re-write their extensions. At that stage, we dropped support for Safari. Regards Click Studios
  23. Issue: The Passwordstate Windows Service executes back ground tasks such as password resets, heartbeats, reports and email notifications. If you notice that the Passwordstate Windows service is in a stopped state, this could be due to your AV solution quarantining the executable for the Windows Service. Cause: In build 9708, we moved the passwordstate.exe file to a new location, in a dedicated folder. Moving this file has resulted in some AV solutions to quarantine the file. Fix: Step 1: Check if the c:\inetpub\passwordstate\windowsservice\passwordstate.exe file exists. If it doesn't proceed to step 2. If it exists, but the service will still not start, please log a support call with Click Studios as this will be a different issue. Step 2: On your Passwordstate webserver, download the zip file from here and extract it: https://www.clickstudios.com.au/downloads/temp/PasswordstateWindowsService_Build9753.zip Step 3: Place it in the c:\inetpub\passwordstate\WindowsService folder Step 4: Run the upgrade again straight away by following section 3 in this guide: https://www.clickstudios.com.au/downloads/version9/Upgrade_Instructions.pdf Regards, Support
  24. Hi Jeff84, Unfortunately there's no direct upgrade path from Version 5 to the latest build, so we'd recommend installing a new version of Passwordstate on the new server, in the new domain, and then exporting the passwords from the old instance and import them into the new instance. You'll then need to set up your new domain details and users and apply permissions throughout the software accordingly. You can apply your current licenses to the new instance whilst doing this migration to open up the same amount of licenses. Hopefully this works and happy to discuss more over our support email if you would prefer to contact us there. Depending on how many folders and password list you have and how you have your systems structured, we may be able to script the creation of these objects when using the bulk import feature? Our support can be contacted via this page: https://www.clickstudios.com.au/support.aspx Regards, Support
  25. Hello Everyone, Today we have released build 9753. For full details, please refer to our changelog here https://www.clickstudios.com.au/passwordstate-changelog.aspx Regards Click Studios
×
×
  • Create New...