You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Dilli Arumugam (JIRA)" <ji...@apache.org> on 2015/04/03 19:37:54 UTC
[jira] [Resolved] (RANGER-369) ranger agent connection to ssl
enabled ranger admin fails
[ https://issues.apache.org/jira/browse/RANGER-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dilli Arumugam resolved RANGER-369.
-----------------------------------
Resolution: Fixed
commit 984fd5b861c131f94a10002f064cfab2d1899d6a
> ranger agent connection to ssl enabled ranger admin fails
> ---------------------------------------------------------
>
> Key: RANGER-369
> URL: https://issues.apache.org/jira/browse/RANGER-369
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.5.0
> Reporter: Dilli Arumugam
> Assignee: Dilli Arumugam
> Fix For: 0.5.0
>
>
> Ranger agent connection to ssl enabled ranger admin fails.
> The root cause is mismatched names between config parameter name in service def json file and parameter name used in org.apache.ranger.common.ServiceUtil.java
> service def file uses config param name:
> certificate.cn
> ServiceUtil looks up by param name:
> commonNameForCertificate
> We have to use consistent name,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)