You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/05/02 21:00:05 UTC

[jira] [Commented] (AMBARI-20909) Server Error in Ambari UI, when trying to login as a pam user due to user name conflict

    [ https://issues.apache.org/jira/browse/AMBARI-20909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993733#comment-15993733 ] 

Hadoop QA commented on AMBARI-20909:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12866043/AMBARI-20909-Branch2.5.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11567//console

This message is automatically generated.

> Server Error in Ambari UI, when trying to login as a pam user due to user name conflict
> ---------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20909
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20909
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Anita Gnanamalar Jebaraj
>            Assignee: Anita Gnanamalar Jebaraj
>         Attachments: AMBARI-20909-Branch2.5.patch
>
>
> Create a local user "test" in Ambari
> Create a system user "test" with different password  
> Trying to authenticate via pam in Ambari UI as user "test" throws Server Error in Ambari UI, without any error in Ambari-server logs
> Also the UI gets stalled and not even able to login as admin user unless the browser cache is removed or Ambari UI is opened in a new browser page
> Ambari doesn't allow creating users with same user name but different types(Local/pam), so this should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)