[
https://issues.apache.org/jira/browse/AMBARI-17899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-17899:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk:
{code:java}
commit deb0341474c8b81441cdc3be820889133393627a
Author: oleewere <[email protected]>
Date: Mon Aug 1 09:48:38 2016 +0200
AMBARI-17899. Login flow break when only ldap auth is enabled. (Hayat
Behlim via oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit 5b49440e947dc46558b0c4840bac90b0cf6cb41c
Author: oleewere <[email protected]>
Date: Mon Aug 1 09:48:38 2016 +0200
AMBARI-17899. Login flow break when only ldap auth is enabled. (Hayat
Behlim via oleewere)
{code}
> Login flow break when only ldap auth is enabled
> -----------------------------------------------
>
> Key: AMBARI-17899
> URL: https://issues.apache.org/jira/browse/AMBARI-17899
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
> Affects Versions: 2.4.0
> Reporter: Hayat Behlim
> Assignee: Hayat Behlim
> Labels: patch
> Fix For: 2.4.0
>
> Attachments: AMBARI-17899.patch
>
>
> *Actual :*
> When property logsearch.auth.ldap.enable=true and other authentication
> methods are disabled then user can login with any username and password.
> *Excepted*
> User should login only for valid ldap users.
> #set properties value to reproduce this issue
> logsearch.auth.file.enable=false
> logsearch.auth.ldap.enable=true
> logsearch.auth.simple.enable=false
> logsearch.auth.external_auth.enable=false
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
