Feature Request: Add Delinea Secret Server as a native Secret Manager integration
Repository: usebruno/bruno
Author: nojetlag
### I have checked the following:
- [x] I've searched existing issues and found nothing related to my issue.
### This feature
- [ ] blocks me from using Bruno
- [x] would improve my quality of life in Bruno
- [ ] is something I've never seen an API client do before
### Describe the feature you want to add, and how it would change your usage of Bruno
### Describe the feature you'd like
I would like to see **Delinea Secret Server** (formerly Thycotic Secret Server) added as a native secret provider in Bruno's Secret Manager (available in Bruno Ultimate).
Currently, Bruno supports:
- HashiCorp Vault (Token + AppRole)
- AWS Secrets Manager
- Azure Key Vault
Many enterprises (especially in regulated industries like finance, healthcare, and government) use **Delinea Secret Server** as their primary on-premises or cloud secret management solution. Adding native support would allow users to dynamically fetch secrets without storing them locally or writing custom scripts.
### Use case
- Teams using Bruno for API testing and automation want to pull credentials, API keys, tokens, certificates, etc., directly from Delinea Secret Server.
- This would work for both **Bruno Desktop** and **Bruno CLI** (similar to the existing Vault, AWS, and Azure integrations).
- Support for common authentication methods: Windows Authentication, OAuth2 / API Key, or username/password.
- Ability to reference secrets by Secret Name, ID, or Folder path.
- Optional caching for performance (like existing providers).
### Why this matters
Delinea Secret Server has a well-documented REST API, so implementation should be straightforward. It would make Bruno even more enterprise-friendly and close the gap with tools that already support broader secret manager ecosystems.
### Proposed implementation outline (optional)
- Add "Delinea Secret Server" as a new option in the Secret Manager configuration UI.
- Support configuration fields such as:
- Server URL (e.g. `https://secretserver.company.com`)
- Authentication method
- Secret path / Name / ID
- Optional folder filtering
- Reuse the existing secrets fetching and variable injection mechanism.
### Additional context
- I am currently using workarounds (pre-request scripts calling the Delinea REST API or external scripts to populate `.env`), but a native integration would be much cleaner, more secure, and consistent with other providers.
- There is growing demand for more secret manager options (see related issues: #377, #6386, #5310, #1841, etc.).
### Are you willing to help?
- [X] Yes, I can help test the integration
---
**Environment**
- Bruno version: [e.g. v3.2.2]
- OS: [Windows]
Thank you for considering this request!
### Mockups or Images of the feature
_No response_