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

Facing Authorization issue to up the Eclipse Ditto using Helm #1841

Closed
kalyanibharadwaj opened this issue Dec 13, 2023 · 3 comments
Closed
Labels

Comments

@kalyanibharadwaj
Copy link

kalyanibharadwaj commented Dec 13, 2023

I'm encountering an authorization issue after deploying Eclipse Ditto using the Helm Chart with default values with docker desktop. The deployment process completed without any errors, and I followed the instructions to port forward and obtained the passwords for the "devops" and "status" accounts.
However, upon attempting to access "http://devops:${DEVOPS_PWD}@localhost:8080/devops," I receive the message, "The requested resource could not be found."

Additionally, I am unable to log in at "localhost:8080/ui" using the "devops" or "status" passwords.

I would greatly appreciate any assistance in resolving this issue and would welcome any insights on where the problem may lie.

@kalyanibharadwaj kalyanibharadwaj changed the title Facing issue to up the Eclipse Ditto using Helm Facing Authorization issue to up the Eclipse Ditto using Helm Dec 13, 2023
@kalyanibharadwaj
Copy link
Author

kalyanibharadwaj commented Dec 14, 2023

adding additional information:
Helm Chart Version: 3.4.2

curl -i -X GET "http://devops:${DEVOPS_PWD}@localhost:8080/devops"
HTTP/1.1 404 Not Found
Server: nginx/1.25.3
Date: Thu, 14 Dec 2023 02:23:21 GMT
Content-Type: text/plain; charset=UTF-8
Content-Length: 42
Connection: keep-alive
Access-Control-Allow-Methods: GET, POST, PUT, PATCH, DELETE, OPTIONS
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: *

@thjaeckle
Copy link
Member

3.4.2 had an issue with authentication, see #1833

Did you try 3.4.3?

@kalyanibharadwaj
Copy link
Author

observed same issue even with 3.4.3, i spend some time to debug and understand.
once i added the user under hashedBasicAuthUsers: its started working ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants