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

Allow use of 'Organizational CA' #14949

Closed
RickJWagner opened this issue Oct 22, 2019 · 5 comments
Closed

Allow use of 'Organizational CA' #14949

RickJWagner opened this issue Oct 22, 2019 · 5 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Milestone
Backlog - Platform

Comments

@RickJWagner
Copy link
Contributor

Is your enhancement related to a problem? Please describe.

Some institutions use a self-provided Certificate Authority ('Organizational CA'). They will have use cases like "wildcard cert signed by our internal CA on the ingress controller".
Please ensure Che works effectively in such an environment.

Describe the solution you'd like

Wish List #1: Everything just works after proper installation
Wish list #2 (if #1 is not possible): Clear log entries that provide guidance when Certs are rejected, clear documentation on procedures to fix things when it happens

Additional context

Please test this scenario (Organizational CA, OpenShift 4)
@RickJWagner RickJWagner added the kind/enhancement A feature request - must adhere to the feature request template. label Oct 22, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Oct 22, 2019
@l0rd
Copy link
Contributor

l0rd commented Oct 23, 2019

We have already done some work #13869 (comment) but I don't think we have documented it yet (cc @skabashnyuk @sleshchenko).

This is related to #14742 and @vparfonov team's is also working git + tls #14527

@l0rd l0rd added team/platform kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system. and removed kind/enhancement A feature request - must adhere to the feature request template. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 23, 2019
@skabashnyuk skabashnyuk added this to the Backlog - Platform milestone Oct 23, 2019
@che-bot
Copy link
Contributor

che-bot commented Apr 22, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2020
@sleshchenko
Copy link
Member

/remove-lifecycle stale

@sleshchenko
Copy link
Member

I think we can close now this issue as implemented. https://www.eclipse.org/che/docs/che-7/installing-che-in-tls-mode-with-self-signed-certificates/

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 23, 2020
@che-bot
Copy link
Contributor

che-bot commented Oct 28, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 28, 2020
@che-bot che-bot closed this as completed Jan 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
Backlog - Platform
Development

No branches or pull requests
5 participants
@RickJWagner @l0rd @skabashnyuk @sleshchenko @che-bot