
Sarge
Members-
Content Count
165 -
Joined
-
Last visited
-
Days Won
4
Sarge last won the day on July 5 2019
Sarge had the most liked content!
About Sarge
-
Rank
Senior Member
Recent Profile Visitors
1295 profile views
-
Thanks, what build is that available on? We're on 8650 and that report doesn't appear to be available via the API doco?
-
Hi, Is there a method to pull a list of Managed hosts (IE: Those that have a password entry managed) from the API? The current documentation only seems to show basic host information.
-
Hi There, We have multiple authentication domains attached to Passwordstate, some users continuously forget which domain to use for authentication, thus raising constant support issues for PEBKAC. Is it possible to use a browser cookie (or some other mechanism) to remember the default domain the user chooses after a successful login?
-
Microsoft Authenticator - Push Notifications
Sarge replied to Pete's topic in Feature Requests - Completed
+1 -
Sarge reacted to a post in a topic: API for (global) addressbook and self destruct message portal
-
Agreed. Notes being encrypted makes searching more difficult.
-
Ah beautiful, didn't know that existed Thanks!
-
Hi Guys, Whats the process for upgrading Passwordstate, when there are 2 * Application Servers, 2 * Self Destruct Servers, 2 * Reset portals & 1 * Gateway server? What needs to be upgraded first? 2 * Database Servers One per datacenter, Active/Cold with automatic failover. 2 * Application Servers One per datacenter, presented through load balancers to distribute traffic evenly and provide Active/Active HA services. 2 * Self Destruct Servers One per datacenter, presented through load balancers, all traffic routed to node 1, only rou
-
parrishk reacted to a post in a topic: MFA - "Remember Me" Option
-
No, the self-destruct message data is stored in a SQLLite database on the Self-Destruct web server, Passwordstate web server pushes data to it. If you round robin to two nodes (or more), one of them will get the data (say, self-destruct server1) , while the one the user hits to access the data (self-destruct server2) won't have it. All self-destruct data needs to go to a single node, hence why an Active/Cold setup works.
-
Sort of, if you have the load balancers capable of doing it. Self Destruct uses its own SQL-Lite database where it stores the shared messages/credentials pushed to it by the main Passwordstate website. We have our Self Destruct web sites installed on the same web nodes as Passwordstate, bound to a seperate IP address. Our load balancers then direct all traffic for the self destruct HA URL to node 1 unless that node is offline. This way the self destruct messages are always available until the node is offline. It's HA in an Active/Cold configuration. In a disaster we still maintain
-
Access can be gained via Administration > Password Folders.
-
Have the PWS Launcher, Launch SSH, and other services via WSL
Sarge replied to bjackel's topic in Feature Requests
Agreed. I think this goes right down to the password resets as well. Install WSL on Server 2016/2019 and use the native tools for running the scripts rather than modules (IE: Posh-SSH etc) -
Same for the Google Auth 2FA. The Microsoft Authenticator app supports push notifications, just needs to be implemented on Passwordstate end.