Extension Creation problem

[ArneV]

Im trying to setup my environment to create a SQL Extension.

However i get 2 errors, i guess the first part is due to the second part.

The environment is using a self signd certificate, but how can i skip the validation?

Do i have to somehow mark it localy as a trusted? (Just guessing)

Regards

Arne

[lubrman]

Hi @ArneV 

Is it an extension from the Hub or a custom extension for SQL?

[ArneV]

I'm trying to write my own custom SQL extension.

[t_pawlak]

Hi,
you can't skip validation. With self-signed certificates, you need to:

Add the certificate to the Credential Vault

Dynatrace → Manage→  Credential vault → Ann new credential 
then Credential type: Public certyficate to extension validation

Upload the CA (root or intermediate) or the self-signed cert in PEM format.

Sign the extension package and create the bundle
Dynatrace only accepts signed extensions. For example:

# 1) Package the extension
zip -r extension.zip extension/

# 2) Sign it with your cert and private key
openssl cms -sign \
  -signer ../../dynatrace.crt \
  -inkey ../../dynatrace.key \
  -binary -in extension.zip \
  -outform PEM -out extension.zip.sig

# 3) Bundle both files
zip -r bundle.zip extension.zip extension.zip.sig

Then upload bundle.zip under Extensions

[ArneV]

Sorry i might be slightly confused. When i watch the DT video and follow the guide ( https://www.youtube.com/watch?v=Qy4Ge8HIzEk) They just enter the URL. When i do this for my production environment it works fine. When i do it for my test environment, it does not work.

So it seems it's not in VSCode where i added the path to my keys / certificates that is the issue.

However it seems more to be an issue with VSCode (DT Extension) That will not accept a Self signed certificate when connecting to the environment.

Prod asks for the API key (As expected)

Test still says 

I can try to use your description. However i cannot initialize workspace. For that i "must" use a environment.

[lubrman]

Hi @ArneV 

So you’re using the VS Code Dynatrace extension. The issue is most likely that you don’t have the correct certificate generated for this environment. When you switch between environments within the extension, you also need to add the key and the URL go through the entire setup process again. That should resolve your problem. As it stands, it looks like you’re trying to use a production certificate in the test environment.

[ArneV]

But this is the problem. i cannot add a environment.

It's when i try to add i get the certificate error, it is as if the VSCode / DT Plugin will not accept an environment with a self signed certificate. 

[lubrman]

HI @ArneV 
Therefore, I suggest setting up the extension for this repository again.
It looks like an incorrect URL is being used as if the tenant ID were wrong.

[ArneV · Accepted solution]

Well found some solutions.

Well it's not a wrong URL. It's a correct URL, howver VSCode / Dynetrace extension cannot / Will not work for a SSL certifthat is self signed. In the browser it was marked with exception used to go to webpage, so a clear indication that the SSL somehow was not compleatly good. 

We had however the certification chain for this self signed certificate, when this also was uploaded to DT it worked.

How i can connect to my DT environment / See the extensions / Upload my development. 

Unfortunately the YouTube videos showing how to build a SQL Extension seems to be wrong with the current version.

Removing some code made it possible to build it.