[
https://issues.apache.org/jira/browse/METRON-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671942#comment-16671942
]
ASF GitHub Bot commented on METRON-1844:
----------------------------------------
Github user merrimanr commented on a diff in the pull request:
https://github.com/apache/metron/pull/1246#discussion_r230138602
--- Diff:
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/configuration/metron-rest-env.xml
---
@@ -35,32 +35,29 @@
</property>
<property>
<name>metron_spring_profiles_active</name>
- <description>Active Spring profiles</description>
+ <description>Active Spring profiles. 'ldap' is used to enable
authentication via LDAP.</description>
<display-name>Active Spring profiles</display-name>
- <value/>
- <value-attributes>
- <empty-value-valid>true</empty-value-valid>
- </value-attributes>
+ <value>jdbc</value>
--- End diff --
Are we using a "jdbc" profile anywhere? From what I can tell jdbc
authentication is used by default but we don't actually use a profile for that.
> Allow for LDAP to be used for authentication and roles
> ------------------------------------------------------
>
> Key: METRON-1844
> URL: https://issues.apache.org/jira/browse/METRON-1844
> Project: Metron
> Issue Type: New Feature
> Reporter: Justin Leet
> Assignee: Justin Leet
> Priority: Major
>
> Based on Simon's work from the SSO feature branch, we can pull the LDAP
> portions out in a more standalone manner.
> This should
> * Letting users optionally use LDAP. Backwards-compatibility should be
> maintained for JDBC purposes.
> * Provide the configs necessary for SSL (this is just providing the
> truststore args, Spring takes care of the actual connection)
> * Be configured via Ambari
> * Ensure roles can be mapped appropriately (e.g. ROLE_ADMIN and ROLE_USER).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
