-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not all secrets showing with SecretServer #33
Comments
Please post a screenshot of the full error message. |
Please try adjusting the value on line 103 of the script as follows: you can also pick a different number, which suits your needs. |
Increasing the value seems to show more if not all the credentials and nested folders (as far as I can tell). However I still get notified that some tokens couldn't be resolved. I have it set at 20000, but increased to 20000 by adding 1000 to the value. While I can see more credentials, it does cause the application to lock up upon start up as it reloads the folder. Is there anyway to limit the scrip to pull from only a specific folder? |
@moseala55 Yes, you can filter the secrets by certain criteria, including the folder ID. By default, the body looks like this:
To include only secrets from a specific folder ID, you would adjust those lines like so:
For more information on the supported filter criteria, please see Thycotic's Rest API documentation. |
@moseala55 Did you get the chance to test the suggestion in my last reply? |
Hello, We have the same issue. We use the secret server and our secrets are 5500. I changed the number on the script to 20000 and i still cannot see everything. Is there a different explanation? |
Also, the "filter.folderId" = 123; does not work. |
Connected and authenticated to on prem SecretServer just fine. Not all secrets that I know and have verified I have access too, including secrets that I have created are showing. "Personal Folder" does not show in the list as well. When refreshing the dynamic folder, I do get an information error in the bottom left saying "Some tokens couldn't be resolved".
The text was updated successfully, but these errors were encountered: