Share
ReportHi,
I'm new to this with connectors so I hope there is a simple answer to my question that I just have not learned yet.
Background
We have an API. I've created a Custom Connector towards it in our test environment and it works fine. I've downloaded the artifacts and managed to use them to run paconn create to get another Custom Connector (with a new name) in the same environment with the same settings. So things seems to be working.
The question
However, we're using our ordinary login for authentication, OAuth 2, so in order to run the paconn create command I needed to provide the client secret. Internaly for a testing environment this seems fine, but we are supposed to get this connector certified and I understand it as though I then need to provide this information in the Readme.md file. Providing a secret to our production environment in an open-sorce file seems wrong - so what am I missing?*
Somewhere it seemed like only independent publishers need to provide how to set up for authentication? I've assumed we are considered to be a verified publisher so can we just skip this information? How would certification be possible in that case?
(* I've actually understood it as though we need to provide information on how to create ID and secret, but since we'd like to use our ordinary login I've assumed that we need to use the specific ID and secret. )
All responses (
Answers (
223
