Jump to content

Maria

Members
  • Posts

    8
  • Joined

  • Last visited

Maria's Achievements

  1. You are correct, upgrading to 9630 did indeed solve the issue. Thank you for your help!
  2. I logged in using rts\administrator from another domain-joined computer. Now i get a 401 error: If i try to pass in the username and password, i get the same "You do not have permissions" error. Same for any other domain user. Below you can find the Winapi authentication settings in IIS: I double checked that all users are allowed to use Winapi (Feature Access - API) and that the user has permissions on the object that is requesting. What am i missing here? Thank you for your support.
  3. Hello and thank you for your help. I will provide you with the full context, because what i'm using here is dummy data. So the domain name is rts and the user rts\administrator is the Admin of the Shared Password List, as you can see below: The code that i'm running is a basic one, just trying to retrieve info on just this one Password List: $PasswordstateUrl = 'https://passwordstate/winapi/passwordlists/17' Invoke-Restmethod -Method GET -Uri $PasswordstateUrl -UseDefaultCredentials I'm logged in as this user on a machine in my domain. I don't have any cert issues, but i also tried your sample code and i get the same error. Thank you for your support once again.
  4. To answer your first question, yes, we have, but we also tried turning off any authentication performed by them. And for the second one, the Base URL indeed uses HTTPS. Thank you for four support, Maria
  5. First of all, thank you for your answer. I'm aware that WinAPI won't work for the local account. I was wondering if the AD users, from the trusted domain, can use the WinAPI. They have accounts in Passwordstate and they have permissions over the object. Yet, when i try to query for - let's say a Password List - using -UseDefaultCredentials on any AD user account (which has access to Passwordstate), i get this error: "You do not have permission to view this directory or page" Even if i specify the credentials, i get the same error. Thank you again for your support.
  6. Hello! We tried importing passwords from KeePass and received a 401 - Unauthorized error, as depicted below: Meanwhile, the import using CSV files is successful. We suspect it has something to do with the SAML authentication. One thing to mention is that client requests have 200 OK status, so the 401 might be from the server side. Details: Build: 9595 Checked the Base URL and is the URL used to access Passwordstate Has anyone else experienced this error? Any advice would help. Thank you in advance!
  7. Hello! I have installed Passwordstate using forms-based authentication. Later on, i have connected an AD domain. My question is the following: can i use the winapi with AD domain accounts for this type of installation? Note1: Using API keys works perfectly. Note2: If i try to use the winapi via Powershell with a domain account, i get a "You do not have permission to view this directory or page". Any advice would be useful. Thank you in advance.
  8. I’m considering installing Passwordstate on a server in a Workgroup environment, but keep the features of having AD users connecting to Passwordstate via their AD account, as well as account password reset, etc. As stated in your Security Adminsitrators Manual, I can use a form-based authentication version of Passwordstate and add in AD domains; this way, I can perform local account login, as well as AD login and also be able to perform password resets on domains. Nevertheless, I would like to be certain that this scenario is feasible before starting to deploy the solution. If so, am I to expect any drawbacks?
×
×
  • Create New...