Jump to content

Search the Community

Showing results for tags 'azure'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Essentials
    • Announcements
  • Passwordstate 9.x
    • General Support
    • General Hints and Tips
    • Known Issues
    • Installing Passwordstate
    • Feature Requests
    • Feature Requests - Completed
    • 3rd Party Hardware/Software Knowledge Forum
  • Knowledge Base
    • General FAQs
    • Password Resets
    • Remote Session Launcher
    • App Server
    • Passwordstate API
    • Browser Extensions
    • Password Reset Portal
  • Passwordstate 8.x
    • General Support
    • Feature Requests - Completed

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL





Google Plus Account







Found 3 results

  1. Hi Team, I'm aware you have SAML2 support, and we're currently making good use of that feature, however it'd be great if we could sync user information down from AD based on group membership. Even better if this includes the groups themselves, so we can manage users info and what Passwordstate security groups they get all from Azure AD. I see elsewhere you've suggested to just have your Azure AD sync with an on-prem AD, however that's not a great solution as it then requires that we manage our users from an on-prem AD, when we've moved to decommission such onsite servers. You can easily pull such information from something like Microsoft's own Graph API. List members - Microsoft Graph v1.0 | Microsoft Docs List group transitive members - Microsoft Graph v1.0 | Microsoft Docs This feature would provide huge value for us in allowing us to centrally manage users for Passwordstate.
  2. 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 following this document: https://www.clickstudios.com.au/documentation/move-new-database-server.aspx If you prefer to use an Azure SQL database, please use Microsoft documentation to help with this migration. We haven't fully documented this ourselves but if you install the latest build of SQL Management Studio Tools, there is an option to migrate data from your local SQL database directly to a Azure SQL database. Obviously an empty Azure database will need to be created prior to performing this migration: After migrating your data up to the SQL Azure database, you will need to run these SQL commands when connected to it with SQL Management Studio Tools. This will create the "Passwordstate_User" account and assign it the appropriate permissions. Azure does not allow for the USE statement, so we need to right Click Master Database and select New Query. Execute the following script: CREATE LOGIN passwordstate_user WITH password='Welcome01' GO CREATE USER passwordstate_user FOR LOGIN passwordstate_user WITH DEFAULT_SCHEMA=[dbo] GO Next right click your Passwordstate database, select New Query and run this script: CREATE USER passwordstate_user FOR LOGIN passwordstate_user WITH DEFAULT_SCHEMA=[dbo] GO EXEC sp_addrolemember 'db_owner', 'passwordstate_user'; GO Once you database is moved, you can then use this document to move your Passwordstate website to your Azure Windows server: https://www.clickstudios.com.au/documentation/move-new-web-server.aspx Please note you’ll need to have an external DNS entry which directs all traffic to your Azure web server, and you’ll also need to open a port on your Azure web server firewall to all access for all users. Regards, Support
  3. Hi, With SAML2 in Azure AD in your documentation (Passwordstate_Security_Administrators_Manual.pdf pages 119-125), this works fine but one parameter is missing in Passwordstate: the logout It's not possible to disconnect users only if the user closes his browser. This logout parameter is https://login.microsoftonline.com/common/wsfederation?wa=wsignout1.0 Could you set up the logout parameter in the next build of Passwordstate configuration with SAML2 please ?
  • Create New...