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.

Sign up for GitHub

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

Jump to bottom

AWS provisioner should use configured certificates in the CA #1005

Open
maraino opened this issue Aug 16, 2023 · 0 comments
Open

AWS provisioner should use configured certificates in the CA #1005

maraino opened this issue Aug 16, 2023 · 0 comments
Assignees
@maraino
Labels
bug needs triage Waiting for discussion / prioritization by team
Milestone
v0.26.2

Comments

@maraino
Copy link
Collaborator

maraino commented Aug 16, 2023

Description

When the step cli creates a token for the AWS provisioner, only the certificates hardcoded in the code are used to verify the connection. Instead of doing this, the CA should use the certificates configured in the CA.
@maraino maraino added bug needs triage Waiting for discussion / prioritization by team labels Aug 16, 2023
@maraino maraino mentioned this issue Aug 16, 2023
Merged
@hslatman hslatman added this to the v0.24.5 milestone Aug 22, 2023
@maraino maraino modified the milestones: v0.25.0, v0.25.1 Sep 27, 2023
@hslatman hslatman modified the milestones: v0.25.1, v0.25.2 Nov 29, 2023
@hslatman hslatman modified the milestones: v0.25.2, v0.25.3 Feb 20, 2024
@hslatman hslatman modified the milestones: v0.26.0, v0.26.1 Mar 29, 2024
@hslatman hslatman modified the milestones: v0.26.1, v0.26.2 Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maraino maraino

Labels
bug needs triage Waiting for discussion / prioritization by team
Projects
None yet
Milestone
v0.26.2
Development

No branches or pull requests
2 participants
@maraino @hslatman