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

eKuper API security is not enabled when EdgeX is running in secure mode #4538

Closed
bnevis-i opened this issue Apr 27, 2023 · 1 comment
Closed
Labels
bug Something isn't working security_audit Track issues that are related to CVE/CVSS/CWE auditing etc
Projects

Comments

@bnevis-i
Copy link
Collaborator

🐞 Bug Report

Affected Services [REQUIRED]

eKuiper rules-engine

Is this a regression?

No

Description and Minimal Reproduction [REQUIRED]

As per the EdgeX Microservice Authentication UCR, eKuiper should also be launched in JWT secure mode when EdgeX is also running in secure mode.

Currently, eKuiper API requires no authentication, regardless of how EdgeX is launched.

🌍 Your Environment

Deployment Environment:
EdgeX Version [REQUIRED]:
Anything else relevant?

@bnevis-i bnevis-i added bug Something isn't working security_audit Track issues that are related to CVE/CVSS/CWE auditing etc labels Apr 27, 2023
@bnevis-i bnevis-i added this to New Issues in Security WG via automation Apr 27, 2023
@bnevis-i bnevis-i moved this from New Issues to Icebox in Security WG Apr 27, 2023
@cloudxxx8
Copy link
Member

eKuiper contains the mechanism now, and we provide it the permission to access the secret store token
#4823

Security WG automation moved this from Icebox to Done Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working security_audit Track issues that are related to CVE/CVSS/CWE auditing etc
Projects
No open projects
Security WG
  
Done
Development

No branches or pull requests

2 participants