Skip to content

Conversation

@ahus1
Copy link
Contributor

@ahus1 ahus1 commented Mar 16, 2023

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Documentation
  • Other, please describe:

Closes #1153

Does this PR introduce a breaking change?

  • No
  • Yes

Checklist:

@ahus1 ahus1 self-assigned this Mar 16, 2023
@ahus1
Copy link
Contributor Author

ahus1 commented Mar 16, 2023

Hi @micwron - as there is probably no simple fix for this, I started to updated the documentation.
It would be great if you could have a look and add what's missing.

I wasn't sure where the cacerts file is located in the IDE, and also wasn't sure if users could also use the IDE's UI to add certificate.

Please add your review comments directly in the PR. Thanks!


Add the self-signed certificate or the matching root certificate authority to the IntelliJ's `cacerts` file.

Users can also add certificates via the menu menu:File[Settings... > Tools > Server Certificates]. See https://www.jetbrains.com/help/idea/settings-tools-server-certificates.html[the IDE's help] for details.
Copy link

Choose a reason for hiding this comment

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

This one doesn't work for me, similarly to "Accept non-trusted certificates automatically" - diagrams are still not rendered

== How do I fix this?

Add the self-signed certificate or the matching root certificate authority to the IntelliJ's `cacerts` file.

Copy link

Choose a reason for hiding this comment

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

cacerts file is located here: INTELLIJ_HOME/jbr/lib/security/cacerts.

This solution requires write access to cacerts, which may be an issue on company maintained/protected laptops.

The easiest solution to me is to simply remove kroki-fetch-diagram: true from antora-playbook.yaml

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.

Plugin doesn't use system trust store

2 participants