Bug 1491227
| Summary: | Kibana login problem with usernames having backslash | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ruben Romero Montes <rromerom> | ||||||
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.6.0 | CC: | aos-bugs, jcantril, pdwyer, rmeggins, rromerom, wsun | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.6.z | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
Cause: openshift-elasticsearch-plugin improperly handles usernames with back slash
Consequence: Users are unable to access Elasticsearch
Fix: Modify request to convert backslash to forward slash
Result: Users are able to access Elasticsearch with usernames that contain back slashes.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-10-25 13:06:40 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1325317 [details]
screenshot
Is this a duplicate of 1456584? It doesn't seem to be the same error. This one is:
Illegal Unicode escape sequence near index 6
test\\user
^
The other error was related to spaces in the names and the error message was:
com.floragunn.searchguard.tokeneval.MalformedConfigurationException: no bypass or execute filters at all
I think the error message is unrelated to the login issue. Created attachment 1326005 [details]
Request failed to _mget
The response is the following:
{
"error":{
"root_cause":[
{
"type":"pattern_syntax_exception",
"reason":"Illegal Unicode escape sequence near index 6\ntest\\user\n ^"
}
],
"type":"pattern_syntax_exception",
"reason":"Illegal Unicode escape sequence near index 6\ntest\\user\n ^"
},
"status":400
}
After that, when I refresh I am redirected to the status page with the following message for the elasticsearch plugin: elasticsearch 1.0.0 [pattern_syntax_exception] Illegal Unicode escape sequence near index 6 test\user ^ The issue is in the SG plugin that is unable to handle user names with a slash. Created: https://github.com/fabric8io/openshift-elasticsearch-plugin/pull/101 which converts the back slash to forward for ES use Verified and pass on images v3.6.173.0.48. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3049 |
Description of problem: Having a valid OpenShift user with a backslash in the username (e.g. test\user) generally coming from an ActiveDirectory is preventing the users from login in with the following error: {"type":"log","@timestamp":"2017-09-13T10:55:48Z","tags":["status","plugin:elasticsearch.0","error"],"pid":15,"state":"red","message":"Status changed from green to red - [pattern_syntax_exception] Illegal Unicode escape sequence near index 6\ntest\\user\n ^","prevState":"green","prevMsg":"Kibana index ready"} Version-Release number of selected component (if applicable): Dockerfile-openshift3-logging-kibana-v3.6.173.0.21-17 Also reproduced in Dockerfile-openshift3-logging-kibana-3.5.0-33 How reproducible: Always Steps to Reproduce: (no need to synchronize with AD) 1. htpasswd /etc/origin/master/htpasswd test\user -p test 2. Log in to Openshift with this user 3. Create a project with some demo pod running 4. Click "View Archive" Actual results: Kibana GUI error (see snapshot) Kibana Logs: {"type":"log","@timestamp":"2017-09-13T10:55:48Z","tags":["status","plugin:elasticsearch.0","error"],"pid":15,"state":"red","message":"Status changed from green to red - [pattern_syntax_exception] Illegal Unicode escape sequence near index 6\ntest\\user\n ^","prevState":"green","prevMsg":"Kibana index ready"} Expected results: User can view the logs normally in Kibana Additional info: