How to create a Machine Connector that doesn't rely on an arbitrary name to attach the certificate?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

How to create a Machine Connector that doesn't rely on an arbitrary name to attach the certificate?

L0 Member

I am building a new machine connector for use with Certificate Manager SaaS.

The Connecter breaks the certificate install process into four steps:

  • testConnection
  • installCertificateBundle
  • configureInstallationEndpoint
  • discoverCertificates

Each as seperate API calls to the connector on the vSat.

It is designed in a way that requires a user to give the certificate a name on the destination system.

installCertificateBundle is intended to put the certificate on the destination with the given name.

configureInstallationEndpoint is then intended to use that given name to attach the certificate to a web service/interface etc.

I believe this is all beased on the original F5 Big-IP connector so appears to be designed around that platform specifically.

 

The sysem I am building this for has no naming system for the certificates. It uniquely identifies them by their sha256 thumb-print.

As no information about the certificate except the user defined name is passed in the configureInstallationEndpoint call how can I identify the certificate that has just been installed in order to use it in the configureInstallationEndpoint stage and assign it to the service I need to?

 

 

1 accepted solution

Accepted Solutions

L3 Networker

Hi @Simon Meadows​. Names are not required and configureInstallationEndpoint has a different payload than that:

 

Field_Content_versions_oct20__068Vy000010i6KcIAI.pngIf the sha256 thumbprint is what you need to configure the endpoint after the certificate has been installed, you can return that in the response for installCertifiateBundle and that will be provided to configureInstallationEndpoint.

View solution in original post

1 REPLY 1

L3 Networker

Hi @Simon Meadows​. Names are not required and configureInstallationEndpoint has a different payload than that:

 

Field_Content_versions_oct20__068Vy000010i6KcIAI.pngIf the sha256 thumbprint is what you need to configure the endpoint after the certificate has been installed, you can return that in the response for installCertifiateBundle and that will be provided to configureInstallationEndpoint.

  • 1 accepted solution
  • 27 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!