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

Add an ability to configure public accessible paths for Che secure servers #10400

Closed
sleshchenko opened this issue Jul 12, 2018 · 0 comments
Closed

Add an ability to configure public accessible paths for Che secure servers #10400

sleshchenko opened this issue Jul 12, 2018 · 0 comments
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.

Comments

@sleshchenko
Copy link
Member

Description

Since JWT Proxy supports configuring exclude rules for verifier (here is the corresponding issue #10312) it is needed to introduce attribute of server config that will be used for configuring exclude rules for JWT proxy verifier.
Also, it is needed to update servers configuration of terminal, exec-agent, wsagent to make health check endpoints public accessible.

OS and version:

Diagnostics:
@sleshchenko sleshchenko added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform labels Jul 12, 2018
@slemeur slemeur mentioned this issue Jul 12, 2018
Closed
20 tasks
@mshaposhnik mshaposhnik mentioned this issue Jul 18, 2018
Merged
@skabashnyuk skabashnyuk mentioned this issue Jul 18, 2018
Closed
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mshaposhnik @sleshchenko