Skip to content

[Certified Connector] Keeper Secrets Manager#4230

Open
mnaqvi-ks wants to merge 3 commits into
microsoft:devfrom
mnaqvi-ks:add-keeper-secret-manager
Open

[Certified Connector] Keeper Secrets Manager#4230
mnaqvi-ks wants to merge 3 commits into
microsoft:devfrom
mnaqvi-ks:add-keeper-secret-manager

Conversation

@mnaqvi-ks

Copy link
Copy Markdown

New Certified Connector: Keeper Secrets Manager

Overview

This PR adds the Keeper Secrets Manager certified connector for Microsoft Power Automate and Azure Logic Apps.

Keeper Secrets Manager (KSM) is a cloud-based, zero-knowledge secrets management platform built for DevOps and IT teams. This connector enables automated workflows to securely retrieve, create, and update secrets stored in a Keeper Vault — without hardcoding credentials in logic apps or flows.

All API calls are routed through a customer-deployed Azure Function middleware, ensuring that neither Microsoft nor Keeper ever processes plaintext secret values.

Publisher

Keeper Security, Inc.

Supported Operations

Operation Description
List Secrets Returns all secrets accessible to the KSM application, including UID, title, type, and folder UID
Get Secret Retrieves full details of a single secret by UID, including login, password, URL, notes, and custom fields
Create Secret Creates a new login-type secret in a specified shared Keeper Vault folder
Update Secret Updates one or more fields on an existing secret; omitted fields are unchanged
List Folders Returns all folders accessible to the KSM application, including UID, name, and parent folder UID

Architecture

The connector communicates with a customer-deployed Azure Function App (middleware) that wraps the Keeper Secrets Manager SDK. Each customer deploys their own middleware instance, scoped to their own Keeper vault credentials. The Function App URL and host key are provided as connection parameters — no shared infrastructure is used.

Artifacts

  • apiDefinition.swagger.json
  • apiProperties.json
  • readme.md
  • icon.png

Validation

  • Swagger validated without errors
  • All 5 operations tested end-to-end against a live Keeper vault
  • Icon meets dimension, background color, and logo size requirements (200x200px, #000000 background)
  • dynamichosturl policy configured — host is overridden per connection parameter
  • No hardcoded credentials or tenant-specific values in any artifact
  • Publisher verified: Keeper Security, Inc.

Testing

All operations were tested against a live Keeper vault via the deployed Azure Function middleware:

  • List Secrets — returns full secret inventory with UIDs and folder mappings
  • Get Secret — retrieves login, password, URL, notes, and custom fields by UID
  • Create Secret — provisions a new login-type record in a shared folder
  • Update Secret — patches individual fields without overwriting unrelated data
  • List Folders — returns full folder hierarchy with parent/child relationships

Related Links

@mnaqvi-ks mnaqvi-ks requested a review from a team as a code owner July 6, 2026 15:20
@mnaqvi-ks

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree company="Keeper Security, Inc."

@vmanoharas vmanoharas left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @mnaqvi-ks,

Please update swagger file and address the comments.

"title": "Keeper Secrets Manager",
"description": "Keeper Secrets Manager is a cloud-based, zero-knowledge secrets management platform for DevOps and IT teams. Securely retrieve, create, and update secrets (credentials, API keys, passwords) stored in your Keeper Vault and automate secret lifecycle workflows.",
"x-ms-api-annotation": {
"status": "Production"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change this from Production to Preview

Comment thread certified-connectors/Keeper Secrets Manager/apiDefinition.swagger.json Outdated
@mnaqvi-ks mnaqvi-ks requested a review from vmanoharas July 10, 2026 14:17

@vmanoharas vmanoharas left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dear Partner,

Congratulations your PR is approved !! We are proud to announce the Brand-New Certification experience for you to certify Power Platform Copilot Connectors.

As next steps:

  1. Learn about the new certification experience- Get your Power Platform connector and plugin certified - Overview
  2. Package your connector files- Prepare Power Platform connector and plugin files for certification
  3. Validate the package for structure before submitting the package for certification to Partner Center - Run Package Validator tool
  4. Initiate a certification request in Partner Center- Verified publisher certification process
  5. Ensure your connector files comply to the Marketplace policies here- 5000 Power Platform Connector Policies for Marketplace and also 1000 Marketplace policies(as applicable)
  6. Test your connector post certification to provide go-live for deployment- Testing Guidelines
  7. If you wish to Update your connector in future- Updating Guidelines
    For any queries or concerns please get in touch with us on certificationteam@microsoft.com

Many thanks,
Power Platform
Copilot connector & plugin certification team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants