You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Akira Ajisaka (Jira)" <ji...@apache.org> on 2020/10/30 11:20:00 UTC

[jira] [Updated] (AMBARI-22697) Throw exception when keytab creation fails due to wrong configuration of key encryption types

     [ https://issues.apache.org/jira/browse/AMBARI-22697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Akira Ajisaka updated AMBARI-22697:
-----------------------------------
    Fix Version/s: 2.7.0
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

The PR is merged into 2.7.0 and upper. Closing.
https://github.com/apache/ambari/commit/b434663cc8f15852b11b8e8607b105f71c360832

> Throw exception when keytab creation fails due to wrong configuration of key encryption types 
> ----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-22697
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22697
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>            Reporter: Akira Ajisaka
>            Assignee: Akira Ajisaka
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>         Attachments: AMBARI-22697.001.patch
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> When kerberos key encryption type is wrong, kerberos service check fails by kinit failure. Now it is difficult to find that the root cause (misconfiguration of key encryption type) because keytabs look to be created successfully. (Actually keytabs are not created successfully, they are only 2-byte files)
> I'm thinking we should display error message or throw exception when keytab creation fails due to wrong key encryption type.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)