-
Notifications
You must be signed in to change notification settings - Fork 85
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
AD Secret Engine - keep or remove? #39
Comments
I'd be in favor of this as it reduces our maintenance burden. |
Closed
cipherboy
pushed a commit
to cipherboy/openbao
that referenced
this issue
Jan 21, 2024
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.41.0 to 1.53.0. - [Release notes](https://github.com/grpc/grpc-go/releases) - [Commits](grpc/grpc-go@v1.41.0...v1.53.0) --- updated-dependencies: - dependency-name: google.golang.org/grpc dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
cipherboy
pushed a commit
to cipherboy/openbao
that referenced
this issue
Jan 21, 2024
…mpatible (openbao#39) Bumps [github.com/docker/docker](https://github.com/docker/docker) from 24.0.5+incompatible to 24.0.7+incompatible. - [Release notes](https://github.com/docker/docker/releases) - [Commits](moby/moby@v24.0.5...v24.0.7) --- updated-dependencies: - dependency-name: github.com/docker/docker dependency-type: indirect ... --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
We chose to remove it in the plug-in proposal #64 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Active Directory Secret Engine was deprecated in Vault 1.13 and is pending removal in Vault 1.19. It needs to be decided how OpenBao is going to handle this Engine. Are we going to drop it as well since it can be replaced by the newly added LDAP Engine? Or are we going to keep supporting it?
If we drop it, I think we should do so immediately since we are probably not going to keep following the Vault versioning scheme and deprecation schedule
The text was updated successfully, but these errors were encountered: