Jump to content

Search the Community

Showing results for tags 'winapi'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Google Plus Account


Location


Interests


Biography


Location


Interests


Occupation

Found 3 results

  1. Hi, i am currently trying to set, update or delete folder permissions through the api and winapi. The connection is working properly and if i forget to add any Apply* property or the folder is not manually managed i am getting the appropriate error message from the api. But if all properties are given and correct i only get the default error page as response from the api. I have tested all ApplyPermissionsFor* with no success. My user has admin permissions to the folder, manually adding Administrator permissions for group/user is working. The ErrorConsole does not show up any new errors. Can someone/support please test that behavior? Is the folderpermissions api method working? Example Test Code from the official API Documentation (Change: FolderID, PasswordStateURL and ApplyPermissionsForSecurityGroupName): $PasswordStateURL = 'https://passwordstate/winapi' $jsonData = ' { "FolderID":"253", "Permission":"A", "ApplyPermissionsForSecurityGroupName":"LG_PasswordState_Security_Admins" } ' $result = Invoke-Restmethod -Method Post -Uri $PasswordstateURL'/folderpermissions' -ContentType "application/json" -Body $jsonData -UseDefaultCredentials Verbose: VERBOSE: POST https://passwordstate/winapi/folderpermissions with 127-byte payload VERBOSE: received 19365-byte response of content type text/html VERBOSE: Content encoding: utf-8 ErrorPage Response: generalerror.aspx?aspxerrorpath=/winapi/folderpermissions Thanks, René
  2. Hi, i am developing extended powershell functions for communicating with the api. I try to stick to your API documentation for the properties here. It just seems to me that the API documentation is not up to date or does not contain all options of the individual methods, is that possible? My primary question: Is the API documentation up-to-date or, due to the fact that i want to integrate all current possible options, should I also test all options that are not documented? Furthermore I have already found some bugs in the API documentation. I would send you a list here as soon as I am done with it. An example based on the passwordlists api method: For example, the option Guide that is missing in your documentation, is working. Other options that also not available in your documentation like the following are not working: PasswordStrengthPolicyID PasswordGeneratorID PreventBadPasswordUse PasswordResetEnabled AllowExport Example query: You can see that the above mentioned options are not working (Compare Query <-> Response) body: { "PasswordList": "TestPublicList", "Description": "Test public password list", "CopySettingsFromPasswordListID": "", "CopySettingsFromTemplateID": "", "CopyPermissionsFromPasswordListID": "", "CopyPermissionsFromTemplateID": "", "NestUnderFolderID": 45, "LinkToTemplate": "", "SiteID": 0, "ApplyPermissionsForUserID": "domain\\user", "ApplyPermissionsForSecurityGroupID": "", "ApplyPermissionsForSecurityGroupName": "", "ImageFileName": "protect.png", "PasswordGeneratorID": 10, "PasswordStrengthPolicyID": 4, "PreventBadPasswordUse": false, "AllowExport": false, "PasswordResetEnabled": true, "Permission": "A", "Guide": "testguide" } Response: PasswordListID : 219 PasswordList : TestPublicList Description : Test public password list ImageFileName : protect.png Guide : testguide AllowExport : True PrivatePasswordList : False TimeBasedAccessRequired : False NoApprovers : 1 DisableNotifications : False PasswordStrengthPolicyID : 1 PasswordGeneratorID : 0 CodePage : Using Passwordstate Default Code Page PreventPasswordReuse : 5 AuthenticationType : None Required AuthenticationPerSession : False PreventExpiryDateModification : False SetExpiryDate : 0 ResetExpiryDate : 0 PreventDragDrop : True PreventBadPasswordUse : True ProvideAccessReason : False TreePath : \Services\Domain\Test TotalPasswords : 0 GeneratorName : Using user's personal Password Generator Options PolicyName : Default Policy PasswordResetEnabled : False ForcePasswordGenerator : False HidePasswords : False ShowGuide : False EnablePasswordResetSchedule : False PasswordResetSchedule : 00:00 AddDaysToExpiryDate : 90 SiteID : 0 SiteLocation : Internal OneTimePasswords : False EDIT: As workaround you can add the option "CopySettingsFromTemplateID": 1 to your json, so the settings will be copied from the specified TemplateID. Thanks, René
  3. Hi, It would be great if the API had a method to create, delete and edit templates (incl. custom fields content and values). We would like to automate most of the work in PasswordState as much as possible and reasonable. We have some special template settings and we use all generic fields, so if we want to change the contents of the generic fields or the password list settings, we would like to change this via the API/WinAPI and our CI/CD pipelines. For example, we have a "Customers" field that contains all customer names. This list is edited from time to time and must be changed in all password lists. This is not so nice to do manually with a lot of lists and the error rate (typos). Please vote for this feature request and stay healthy. Thanks, René
×
×
  • Create New...