All Activity
This stream auto-updates
- Last week
-
Awesome - thanks for the update.
-
Hi Guys, We did notice a small difference between the manual and scheduled backups today, so we've now fixed this and you can open the zip file from both in Windows. It still seems to take a while to open in Windows Explorer, which is really odd, but other zip programs seem to be fine. We'll have this fix in the next release. Regards Click Studios
-
Hi Fabian, We're using a pretty copy zip library for this feature. If you use 7-zip does it work as expected? We'll see if there's an update to this library we can apply. Regards Click Studios
-
Hi All I'm experiencing the same issue. The ZIP file is not extractable or even browsable with the windows explorer. When I open the ZIP file with the tool IZArc, it looks like below (two empty folders are in the path). With IZArc I'm able to extract the ZIP file, but then the folder and file stucture is completely messed up. When I use the Powershell command Expand-Archive (as mentioned above), I can successfully extract all the files with the correct folder structure. Best regards, Fabian
-
Hi, it looks like 7zip was able to extract this archive. Odd - I am not sure why it won't work with the built in tool from windows. I tried expanding with the powershell cmdlet expand-archive and that seems to be successful as well.
-
Hi rene, We just updated that other post with an interim fix for this bug. Thanks very much. Regards Click Studios
-
Hello, Sorry you're having some issues with this. This is very unusual behavior, and we've never experience this before. Can you tell us what build of Passwordstate you're using, and what Zip program - maybe try something like 7-zip to see if that makes any difference? Regards Click Studios
-
How to make Passwordstate work on a new URL on the same server
support replied to Simon's topic in General Support
Thanks for sharing Simon -
Hi Thomas, I think the Generic Fields on Password Lists would be the best option for this. You don't need to enable the List for resets, or associate with any hosts, and the Generic Fields gives you different data types and encryption options as well. Do you think this is a possibility? Regards Click Studios
-
I believe its the same issue as in this post. I will wait for the update and see if it resolves the issue
-
Remote Session launcher and Novell Clients
findusHai replied to findusHai's topic in General Support
Yeah thats what i thought, we only have one costumer that uses Novell as well. but thanks for the fast answer -
How to make Passwordstate work on a new URL on the same server
Simon replied to Simon's topic in General Support
I had forgotten to say that had already had to add firewall exception for port 443 to get this far so had already triple checked everything mentioned above. Based on your assertion that it should just work I did some experiments and made it work by using a new DNS name. We were using the same DNS name as the server name and this seemed to be the cause of the issue when trying to use FQDN to access the application from a browser. FIX = Create a DNS CNAME for the server, added this to IIS website binding on https port 443 with our domain wild card cert. Did not need to add this new name to authorised servers and can access on this new DNS name. Just need to update System Settings - miscellaneous - base URL so any links get the new DNS name. I hope this is of help to someone. Regards Simon -
Hello, I am experiencing an issue where the scheduled backup zip folder is empty although the size of the file is ~179 MB, and when trying to extract it I get the following error: The Compressed (zipped) Folder 'folder name' is invalid. However, there is no issue when doing a manual backup through Passwordstate.
-
sysadmin-z joined the community
-
Hi guys, Lately we've been storing things like crypto-disk PINs and Java keystore passwords in PasswordState. We've had to shoehorn these passwords into an existing password type, but that's suboptimal. Would it be possible for you guys to build in a standard "dumb" password type? Something that will never be auto-managed, nor heartbeated. Something not tied to a hostname, nor to a username. Just a PIN/Password/Whatever. I could try and define my own type, but it'd be nicer if it was in the product. Cheers, Thomas
-
How to make Passwordstate work on a new URL on the same server
support replied to Simon's topic in General Support
Hi Simon, Generally all that's require is: Change the Port binding from 9119 to 443 Change the Host Name binding to match the DNS entry you've created Select the new certificate for the HTTPS binding And make sure there is no firewall blocking 443 It sounds like you've done everything correctly, but can you please double check the items above. If they look correct, please contact us via our support page, as we might need to see some screenshots to figure out what's going on. Regards Click Studios -
Luke joined the community
-
How to make Passwordstate work on a new URL on the same server
Simon posted a topic in General Support
We installed the trial with a self signed certificate, liked it and started using it for real so we want to change to using our domain wildcard certificate so need to add the domain name to the URL name we used. Following various guide and posts on here we made changes (as below) but the new URL does not link to passwordstate but gives HTTP Error 404. In IIS added binding to the password state web site = https://paswordstate.ourdomain.net rather than https://passwordstate:9119 and in Password state and applied our wildcard certificate In Passwordstate under Authorized Web Servers added new domain name, passwordstate.ourdomain.net alongside old name passwordstate In Passwordstate - system setting - miscellaneous specified the new domain name https://passwordstate.ourdomain.net Restarted the IIS site and the service and even the whole server. The new URL works in IIS in that it loads in a browser and the certificate is valid but get HTTP Error 1404. The requested source is not found. It is not an issue with the change of TCPIP port from 9119 to 443 as if bind https://passwordstate to the site in IIS then this works but the URL including the domain name does not connect to the Passwordstate back end. Have tried removing other bindings form IIS site. Have not tried removing other Authorize Server Bindings in Passwordstate as, if does not fix it, would not be able to get back in to change it back. Please can someone suggest how to make this work/ point out what we have missed. Thanks in advance. Simon -
Hi Findus, We've never had any customers mention this to use before, so we're assuming our launcher will not work with - it's really designed for standard RDP and SSH access. Hopefully someone in the community can share some insight though. Regards Click Studios
-
Simon joined the community
-
Hello everyone, it is currently not possible for me to configure the remote session launcher when the Server i want to connect to uses the Novell Client. I always get an error that says "the specified Domain name s wrong". Im using the correct name but i think there are problems passing thourgh all the Information for the Login. Anyone here uses Novell clients and managed to configure the remote session launcher succesfully ? Greetings Findus
-
Hello Pferree, We do not have a Recycle Bin for Password Lists at this stage. The user is prompted twice to confirm the do wish to delete the list, so hopefully no-one will do this by accident. Regards Click Studios
-
Sorry about this Rene - we should have a new build available by the end of this week. Regards Click Studios
-
That's great, but what about a recycle bin for deleted password lists?
-
Hi pferree Every Paaswordlist has its own recyle bin. You find the recycle bin under "List Administrator Actions..." This option should be available on any Passwortlist in the dropdown menu on the bottom right side. Best regards, Fabian
-
There should be a sort of recycle bin to allow a security administrator to recover deleted single passwords or password lists for users. Accidental deletions seem to require a full database restore which can be destructive if a user does not discover their mistake for a period of time. Unless I'm missing an already implemented feature, please look into adding this functionality.
-
Abrie joined the community
-
I am also getting the same error. Rene
- Earlier
-
Hi Rene, Sorry you're having some issues. When you say "I cannot search and select the ou that the servers are sitting in", are you getting some sort of error here, or does it just not find any ous when you click on the 'Look Up' button and search? We might need you to log this call via our support page, as we may need to see some screenshots of your AD Domains - https://www.clickstudios.com.au/support.aspx Regards Click Studios
