Skip to content

Database authorization capability with SSL disabled #387

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
Closed
GrzegorzPustulka opened this issue May 29, 2025 · 0 comments
Closed

Database authorization capability with SSL disabled #387

GrzegorzPustulka opened this issue May 29, 2025 · 0 comments

Comments

@GrzegorzPustulka
Copy link
Contributor

Describe the bug
When the environment variable "ES_USE_SSL" is set to false, there is no possibility of authorization, which results in receiving a 401 error every time. This is caused by the fact that in the _es_config() function, if ES_USE_SSL is set to false, a return is executed before adding authorization. I believe we should provide such a possibility. In my case, OpenSearch is behind a VPN, so disabling SSL should slightly improve performance without compromising security.

To Reproduce
Steps to reproduce the behavior:

  1. Setting ES_USE_SSL=false
  2. OpenSearch with authorization, e.g., using username and password
  3. We get a 401 error - no authorization

Expected behavior
Ability to add authentication with SSL disabled.
@GrzegorzPustulka GrzegorzPustulka mentioned this issue May 29, 2025
Merged
4 tasks
jonhealy1 pushed a commit that referenced this issue May 29, 2025
@GrzegorzPustulka
Database authorization capability with SSL disabled (#388)
b3dabfe 
**Related Issue(s):**
- #387

**Description:**
possibility of authorization with disabled ssl

**PR Checklist:**

- [ ] Code is formatted and linted (run `pre-commit run --all-files`)
- [ ] Tests pass (run `make test`)
- [ ] Documentation has been updated to reflect changes, if applicable
- [ ] Changes are added to the changelog

---------

Co-authored-by: Grzegorz Pustulka <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonhealy1 @GrzegorzPustulka