Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New note about the generation of passphrase protected PKCS#1 keys #3145

Merged
merged 2 commits into from
Jun 29, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/mp/oci/01_oci.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,11 @@ include::{common-deps-page-prefix-inc}[tag=maven-dependency]

== General Configuration

NOTE: If you follow these instructions on how to
https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#two[Generate an API Signing Key],
be advised that Helidon does not currently support passphrase-protected private keys in PKCS#1 format.
If generating a private key using those instructions, use the _no passphrase_ option.

=== Using Helidon MP Properties Configuration

The first option to configure connection to OCI is to directly specify properties in `microprofile-config.properties` file:
Expand Down
5 changes: 5 additions & 0 deletions docs/se/oci/01_oci.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,11 @@ WARNING: Helidon integration with Oracle Cloud Infrastructure is still experimen

== General Configuration

NOTE: If you follow these instructions on how to
https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#two[Generate an API Signing Key],
be advised that Helidon does not currently support passphrase-protected private keys in PKCS#1 format.
If generating a private key using those instructions, use the _no passphrase_ option.

=== Using Helidon SE Properties Configuration

The first option to configure connection to OCI is to directly specify properties in `application.yaml` file:
Expand Down