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

auth/centrify: Centrify auth method is now deprecated #23050

Merged
merged 4 commits into from
Sep 13, 2023
Merged

Conversation

swenson
Copy link
Contributor

@swenson swenson commented Sep 13, 2023

Slated for removal in 1.17

@swenson swenson added this to the 1.15.0 milestone Sep 13, 2023
@swenson swenson requested a review from a team September 13, 2023 16:28
@swenson swenson requested a review from a team as a code owner September 13, 2023 16:28
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Sep 13, 2023
@github-actions
Copy link

Build Results:
All builds succeeded! ✅

@github-actions
Copy link

CI Results:
All Go tests succeeded! ✅

@schavis schavis added the content-lgtm Content changes approved. Merge depends on code review label Sep 13, 2023
Copy link
Contributor

@schavis schavis left a comment

Choose a reason for hiding this comment

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

Content update LGTM

Copy link
Contributor

@tomhjp tomhjp left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -35,6 +35,7 @@ This announcement page is maintained and updated periodically to communicate imp
| SHA-1 certificate signing | v1.11 | v1.11 | v1.12 | Go version 1.18 removes support for SHA-1 by default. As Vault updates its Go version to 1.18, you should plan to move off SHA-1 for certficate signing. Operators can set a Go [environmental variable](/vault/docs/deprecation/faq#q-what-is-the-impact-of-removing-support-for-x-509-certificates-with-signatures-that-use-sha-1) to restore SHA-1 support if they need to continue using SHA-1. It is unknown at this time when Go will remove the environmental variable support. Therefore, we highly encourage you to migrate off of SHA-1 for certificate signing. |[FAQ](/vault/docs/deprecation/faq#q-what-is-the-impact-of-removing-support-for-x-509-certificates-with-signatures-that-use-sha-1)|
| Consul secrets engine parameter changes | v1.11 | N/A | N/A | The `policies` parameter on the Consul secrets engine has been changed in favor of `consul_policies`. The `token_type` and `policy` parameters have been deprecated as the latest versions of Consul no longer support the older ACL system they were used for. | [Consul secrets engine API documentation](/vault/api-docs/secret/consul) |
| Vault Agent API proxy support | v1.14 | v1.16 | v1.17 | Migrate to [Vault Proxy](/vault/docs/proxy/index) by v1.17|
| Centrify Auth Method | v1.15 | v1.17 | v1.17 | Use separate plugin binary, but support will not be available due to lack of updated Centrify libraries. | |
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: I think the lack of updated libraries is more like the reason for deprecating it in the first place?

Suggested change
| Centrify Auth Method | v1.15 | v1.17 | v1.17 | Use separate plugin binary, but support will not be available due to lack of updated Centrify libraries. | |
| Centrify Auth Method | v1.15 | v1.17 | v1.17 | It can still be used as an external plugin, but support will not be available. | |

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think @schavis won't like me changing this to the passive voice :) But, I'll rework that sentence. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content-lgtm Content changes approved. Merge depends on code review hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants