Jump to content

support

Administrators
  • Content Count

    4107
  • Joined

  • Last visited

  • Days Won

    225

support last won the day on September 24

support had the most liked content!

1 Follower

About support

  • Rank
    Administrator

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

13193 profile views
  1. Hello EmilS, With our SAML Authentication, you still need to have "matching" accounts in Passwordstate - they don't need to be AD Accounts, and instead you can create Local Accounts. I've provided a screenshot below for this. And with your SAML Configuration, you need to select which field you want to match against back in Passwordstate, once the SAML Authentication completes successfully i.e. UserID or EmailAddress - most customers pick EmailAddress. As you want a mixture of AD Accounts and Local Accounts in Passwordstate, you may need to use SAML Authentication for all
  2. Hello, Yes, if you are wanting Passwordstate to also backup your database, then you need to modify the Windows Services for SQL Server as instructed - as well for SQL Server Express. There are some changes coming in version 9 which will change this requirement, as long as you are backup up to a Windows Share - if backing up to NAS or SAN Storage, then the requirements will be the same in version 9. Or you can also take your own backups of SQL Server as well - it's not necassary for Passwordstate to do this. Regards Click Studios
  3. Below is some information Click Studio provide to customers when they request some information on moving Passwordstate to an Azure environment: If you intend to move to the cloud, please ensure you keep your current on premise version running, and only shut that down once you have confirmed that you can successfully access your new instance in Azure. The first thing you’ll need to do is determine which kind of database you’ll be using in Azure. You can either install SQL on a Azure Windows Server (just as you would on an On-Premise server), and move your database to it
  4. If you see error codes in the Error Console that contain "Error Code = Illegal operation attempted on a registry key that has been marked for deletion", then this is caused by Windows patches being applied, and a reboot is required to finish the patches. This can affect the Passwordstate Windows Service and various functions within the website. Rebooting your Passwordstate web server will fix this issue. Regards, Support
  5. This feature request was completed in Build 8925. Regards Click Studios
  6. Hi Guys, We're moving this request to Closed, as the Manual Permissions options is being deprecated in version 9, and new Permissions Models of Standard and Advanced are being introduced - with advanced, you can disable inheritance from upper level folders, so we will ensure this setting is added to the API. Regards Click Studios
  7. Hi Guys, We're moving this request to Closed, as the Manual Permissions options is being deprecated in version 9, and new Permissions Models of Standard and Advanced are being introduced - with advanced, you can disable inheritance from upper level folders, so we will ensure this setting is added to the API. Regards Click Studios
  8. Hello, Generally the Domain Name field is used for Exhange internally, and you specify your NetBIOS portion of the domain i.e. bygecko.com. If you're not using Microsoft Exchange, can you try removing this? Also, if you've not selected TLS, then the port number is generally 25 for email. Could you try that also? Regards Click Studios
  9. Hi Than, Thanks for the information. Generally we do not recommend installing Passwordstate on the same server as WSUS or Sharepoint, as removing these roles uninstalls components of IIS which are required for Passwordstate to function. We're not exactly clear on what it removes which breaks Passwordstate, and we have had a look in the past. If you would like to move your Passwordstate install to a different server, you can use the following articles for this: https://www.clickstudios.com.au/documentation/move-new-database-server.aspx https://www.clickstudios.
  10. Hello Marcin, Yes, you can import via CSV in two ways: Directly to a single Password List - under the List Administrator's Actions dropdown list beneath the grid, you will see the Import menu Of into multiple Password Lists at once - although you need to know all the PasswordListID values. You can do this from the screen Administration -> Password Lists -> Perform Bulk Processing We hope this helps. Regards Click Studios
  11. Hello Technic, Yes, it is completely free for 5 users without any time limitation. Regards Click Studios
  12. For any other customers reading this post, we've managed to fix the issues - the two issues were: Disabling Anonymous Authentication in IIS was not working, because Windows Authentication was also disabled - which is not the default setting The customer had the Audience Restriction in Passwordstate set incorrectly - it needs to match the “Identifier (Entity ID)” field in Azure AD Regards Click Studios
  13. Hi Robert, We've sent you an email response with a few questions we need answered, and hopefully this is just a configuration issue because we have many customers using Azure AD and SAML Authentication - the error of "was not found in the directory" sounds like something is not configured correctly. Regards Click Studios
  14. Hi SampoS, Those errors that IIS Session has been prematurely ended can be caused by either Reverse Proxies, AV software on the web server, or possibly a Load Balancer in front of your website. I'd assume the only one of these things that might be applying to you could be AV software, would that be right? If so, could you please disable AV temporarily, and then reset the installer, and run through the initial config again? Resetting the Passwordstate Set up process can be found here: https://www.clickstudios.com.au/community/index.php?/topic/1663-resetting-the-passw
×
×
  • Create New...