[
https://issues.apache.org/jira/browse/KNOX-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171025#comment-16171025
]
Phil Zampino commented on KNOX-1014:
------------------------------------
{quote}Yes, I think it would be better to use something like
ambari.discovery.password - username may not need to be an alias but if you did
I could see ambari.discovery.username{quote}
I can see your point about having an alias for the password that is not the
username. I'm also thinking, for flexibility, that the descriptor should
specify the alias for retrieving the password, rather than requiring
ambari.discovery.password. So, the descriptor would have:
{code:json}
"discovery-user" : "myusername"
"discovery-pwd-alias" : "my.discovery.password.alias"
{code}
What do you think about that?
And I also agree that the hard-coded default username/password should be
removed from the code.
> Service Discovery and Topology Generation Framework
> ---------------------------------------------------
>
> Key: KNOX-1014
> URL: https://issues.apache.org/jira/browse/KNOX-1014
> Project: Apache Knox
> Issue Type: Sub-task
> Components: Server
> Reporter: Phil Zampino
> Assignee: Phil Zampino
> Labels: kip-8
> Fix For: 0.14.0
>
> Attachments: KNOX-1014.patch
>
>
> Implement the foundation for Service Discovery and Topology Generation.
> * Define simple descriptor format (YAML, JSON, etc...)
> * Local simple descriptor and shared provider configuration discovery
> ** Monitor conf/shared-providers, conf/descriptors similar to the way
> conf/topologies is currently monitored.
> * Ambari service discovery (REST API interactions and model construction)
> ** Configuration
> *** How to plug-in discovery implementations
> *** How to configure authentication (credentials/trust) with the service
> registries
> * Topology assembly from simple descriptor and discovery details
> * Topology deployment
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
