You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,15 @@
1
+
# v1.5.0
2
+
## Fixes
3
+
* Patched bug that required the `allow_any_name` or `allowed_domains=[""]` role parameters to issue/sign certificates with no CN.
4
+
5
+
## Chores
6
+
* Upgrade from Go `v1.21` to `v1.22`.
7
+
* Implement more strict golangci-lint policy.
8
+
9
+
## Features
10
+
* If upstream EJBCA API call fails, the HTTP status code is propogated to the Vault user via the Vault API status code.
11
+
* Implement OAuth 2.0 "client credentials" token flow as a supported authentication mechanism to EJBCA.
12
+
1
13
# v1.4.0
2
14
## Fixes
3
15
* Paths that need to write to the Storage backend now forward the request to the primary node. This is important in Enterprise HA deployments where Performance Standby Nodes are allowed to handle read requests/paths.
<ahref="https://ejbca.org"><imgsrc="https://img.shields.io/badge/valid_for-ejbca_community-FF9371"alt="Valid for EJBCA Community"></a>
9
+
<ahref="https://www.keyfactor.com/products/ejbca-enterprise/"><imgsrc="https://img.shields.io/badge/valid_for-ejbca_enterprise-5F61FF"alt="Valid for EJBCA Enterprise"></a>
This API client allows for programmatic management of Keyfactor resources.
11
14
12
-
## Support for EJBCA Vault PKI Secrets Engine
15
+
</h1>
13
16
14
-
EJBCA Vault PKI Secrets Engine is open source and supported on best effort level for this tool/library/client. This means customers can report Bugs, Feature Requests, Documentation amendment or questions as well as requests for customer information required for setup that needs Keyfactor access to obtain. Such requests do not follow normal SLA commitments for response or resolution. If you have a support issue, please open a support ticket via the Keyfactor Support Portal at https://support.keyfactor.com/
###### To report a problem or suggest a new feature, use the **[Issues](../../issues)** tab. If you want to contribute actual bug fixes or proposed enhancements, use the **[Pull requests](../../pulls)** tab.
<!--- Include a description of the project/repository, the purpose of it, what problems it solves, when to use it (and not use it), etc. --->
36
+
## Overview
41
37
42
38
The EJBCA PKI Secrets Engine for HashiCorp Vault enables DevOps teams to request and retrieve certificates
43
39
from EJBCA using HashiCorp Vault, while security teams retain control over backend PKI operations.
@@ -48,49 +44,42 @@ The EJBCA PKI Secrets Engine is a Vault plugin that replicates the built-in Vaul
48
44
requests through EJBCA instead of through Vault. The plugin was designed to be swapped for the built-in Vault PKI secrets engine
49
45
with minimal changes to existing Vault configurations.
50
46
51
-
## Get Started
52
47
53
-
<!--- Insert links to instructions on how to install, configure, etc.
54
-
Example from ejbca-cert-manager-issuer below:
55
48
56
-
* To install the tool, see [Installation](docs/install.md).
57
-
* To configure and use the tool, see:
58
-
* [Usage](docs/config_usage.md)
59
-
* [Customization](docs/annotations.md)
60
-
* [End Entity Name Selection](docs/endentitynamecustomization.md)
61
-
* To test the tool, see [Testing the Source](docs/testing.md).
62
-
--->
49
+
## Support
63
50
64
-
To get started with EJBCA PKI Secrets Engine for HashiCorp Vault, see [Getting Started](docs/getting-started.md).
51
+
In the [Keyfactor Community](https://www.keyfactor.com/community/), we welcome contributions. Keyfactor Community software is open-source and community-supported, meaning that **no SLA** is applicable. Keyfactor will address issues as resources become available.
65
52
66
-
### System Requirements
53
+
* To report a problem or suggest a new feature, go to [Issues](../../issues).
54
+
* If you want to contribute bug fixes or proposed enhancements, see the [Contributing Guidelines](CONTRIBUTING.md) and create a [Pull request](../../pulls).
67
55
68
-
<!--- Insert any requirements in this section. --->
69
-
To run the EJBCA PKI Secrets Engine for HashiCorp Vault, the EJBCA REST API needs to be set up with certain endpoints. There are also requirements on certain versions of Git, Golang, EJBCA, and HashiCorp Vault.
56
+
> Commercial support is available for [EJBCA Enterprise](https://www.keyfactor.com/products/ejbca-enterprise/) customers, who may request escalation by opening up a support ticket through their Keyfactor representative.
70
57
71
-
See the complete list in [System Requirements](docs/getting-started.md#requirements).
58
+
## Requirements
72
59
73
-
## Community Support
74
-
In the [Keyfactor Community](https://www.keyfactor.com/community/), we welcome contributions.
The Community software is open-source and community-supported, meaning that **no SLA** is applicable.
65
+
### To build
66
+
*[Git](https://git-scm.com/)
67
+
*[Golang](https://golang.org/) >= v1.19
77
68
78
-
* To report a problem or suggest a new feature, go to [Issues](../../issues).
79
-
* If you want to contribute actual bug fixes or proposed enhancements, see the [Contributing Guidelines](CONTRIBUTING.md) and go to [Pull requests](../../pulls).
0 commit comments