[jira] [Created] (METRON-1850) Stellar REST function
Ryan Merriman created METRON-1850: - Summary: Stellar REST function Key: METRON-1850 URL: https://issues.apache.org/jira/browse/METRON-1850 Project: Metron Issue Type: New Feature Reporter: Ryan Merriman It would be useful to be able to enrich messages with Stellar using 3rd party (or internal) REST services. At a minimum this function would: * Stellar function available to GET from an HTTP API * Optional parameters for basic auth (user/password) which generate correct Authorization header * Function returns null value for errors, connection failures etc and logs error * Function must provide and use pooled connection objects at the process level * Function must send Accept: application/json header * A global setting must be available to set a proxy for all API calls, and if present the proxy must be used. * Proxy authentication must also be supported using basic auth. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1803) Integrate Cypress with Travis
[ https://issues.apache.org/jira/browse/METRON-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669237#comment-16669237 ] ASF GitHub Bot commented on METRON-1803: Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/1226 Excellent addition, though it looks like this change broke your tests. > Integrate Cypress with Travis > - > > Key: METRON-1803 > URL: https://issues.apache.org/jira/browse/METRON-1803 > Project: Metron > Issue Type: Improvement >Reporter: Tibor Meller >Assignee: Tibor Meller >Priority: Major > > [DISCUSS] thread on the dev mailing list: > [https://lists.apache.org/thread.html/b6a0272c7809c05e8b7aff20171720e8ec76f8a0e9481169c37a4a4a@%3Cdev.metron.apache.org%3E] > JIRA Ticket: https://issues.apache.org/jira/browse/METRON-1803 > This PR adds Cypress.io to our project. It makes us able to run E2E tests, UI > integration tests. Also higher level UI tests with mocked services. > As part of this PR I added tests to cover the following functionalities of > PCAP UI panel: > * checking running jobs on navigating to PCAP tab > * submitting PCAP job request > * requesting job status > * process status in percentage > * getting PCAP JSON > * rendering PCAP table > * showing PCAP details > * navigating across pages > * downloading PDML > * cancelli PCAP query job > * showing filter validation messages > * showing date validation messages > Please consider while reviewing that these tests are not meant to cover all > the details of the functionalities above. The aim here is to extend the test > coverage build up by a large number of Unit Tests with higher level UI tests. > h3. New folders > Cypress files sit in cypress folder. Some of them might look like an empty > placeholder but cypress actively uses all files in this PR. > h4. Integration folder > That contains the actual Cypress tests. The folder name comes from the > Cypress naming convention, however, no real integration tests implemented > here yet (at least no other than the integration of UI components to a whole > application). We could change the name of the folder anytime we like to, but > only one folder applicable. > h4. Fixture folder > The tests are running on mocked data. This makes us able to integrate them > with Travis without the need to having PCAP related services available from > our CI. > Each file in the Fixture folder represents a response to a particular > request. This makes it fairly easy to create and maintain. > h3. How to run tests on your local machine > To run Cypress tests locally please do the following: > # pull this branch to your workspace > # move to metron-interface/metron-alerts folder > # run: npm ci > # run: scripts/start-server-for-e2e.sh > # run: node_modules/cypress/bin/cypress run > or run: node_modules/cypress/bin/cypress open > if you like to use the dashboard. > h3. Travis integration > As part of this PR I modified the package.json in metron-alert to make > Cypress running in Travis. If you like to see the integration working please > check to logs of build step [#3|https://github.com/apache/metron/pull/3]. > Failing Cypress tests brakes the build. > Example of build broken by failing Cypress test: > [https://travis-ci.com/tiborm/metron/builds/86869264] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] metron issue #1226: METRON-1803: Integrate Cypress with Travis
Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/1226 Excellent addition, though it looks like this change broke your tests. ---
[jira] [Commented] (METRON-1815) Separate metron-parsers into metron-parsers-common and metron-parsers-storm
[ https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669033#comment-16669033 ] ASF GitHub Bot commented on METRON-1815: Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/1249 Can we talk about the directory structure and packaging? I think ``` . └── metron-ingest ├── metron-ingest-common ├── metron-ingest-storm ├── metron-parsers └── metron-parsers-common ``` Might be worth thinking about. we can have metron-injest-FOO later > Separate metron-parsers into metron-parsers-common and metron-parsers-storm > --- > > Key: METRON-1815 > URL: https://issues.apache.org/jira/browse/METRON-1815 > Project: Metron > Issue Type: Improvement >Reporter: Justin Leet >Assignee: Justin Leet >Priority: Major > > In order to expose our parsers to 3rd party components (e.g. the discussions > on NiFi and potentially other platforms like Spark), we should > separate the storm-bits into its own project. The metron-parsers-common > project should contain only parser-oriented code, whereas the > metron-parsers-storm project should contain the storm specific code > (e.g. the parser bolt). > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] metron issue #1249: METRON-1815: Separate metron-parsers into metron-parsers...
Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/1249 Can we talk about the directory structure and packaging? I think ``` . âââ metron-ingest âââ metron-ingest-common âââ metron-ingest-storm âââ metron-parsers âââ metron-parsers-common ``` Might be worth thinking about. we can have metron-injest-FOO later ---
[jira] [Commented] (METRON-1803) Integrate Cypress with Travis
[ https://issues.apache.org/jira/browse/METRON-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668855#comment-16668855 ] ASF GitHub Bot commented on METRON-1803: Github user tiborm commented on the issue: https://github.com/apache/metron/pull/1226 You are right @mmiklavc, this is an additional step to our build process. So it makes our build slightly slower. However, the two minutes come from the nature of PCAP. It has a built-in 10-second delay every time we check the job status. What makes these particular tests slower. With mocking out the time I was able to speed them up by 50%. I think it's also a good practice for the upcoming tests to keep them fast with this trick. > Integrate Cypress with Travis > - > > Key: METRON-1803 > URL: https://issues.apache.org/jira/browse/METRON-1803 > Project: Metron > Issue Type: Improvement >Reporter: Tibor Meller >Assignee: Tibor Meller >Priority: Major > > [DISCUSS] thread on the dev mailing list: > [https://lists.apache.org/thread.html/b6a0272c7809c05e8b7aff20171720e8ec76f8a0e9481169c37a4a4a@%3Cdev.metron.apache.org%3E] > JIRA Ticket: https://issues.apache.org/jira/browse/METRON-1803 > This PR adds Cypress.io to our project. It makes us able to run E2E tests, UI > integration tests. Also higher level UI tests with mocked services. > As part of this PR I added tests to cover the following functionalities of > PCAP UI panel: > * checking running jobs on navigating to PCAP tab > * submitting PCAP job request > * requesting job status > * process status in percentage > * getting PCAP JSON > * rendering PCAP table > * showing PCAP details > * navigating across pages > * downloading PDML > * cancelli PCAP query job > * showing filter validation messages > * showing date validation messages > Please consider while reviewing that these tests are not meant to cover all > the details of the functionalities above. The aim here is to extend the test > coverage build up by a large number of Unit Tests with higher level UI tests. > h3. New folders > Cypress files sit in cypress folder. Some of them might look like an empty > placeholder but cypress actively uses all files in this PR. > h4. Integration folder > That contains the actual Cypress tests. The folder name comes from the > Cypress naming convention, however, no real integration tests implemented > here yet (at least no other than the integration of UI components to a whole > application). We could change the name of the folder anytime we like to, but > only one folder applicable. > h4. Fixture folder > The tests are running on mocked data. This makes us able to integrate them > with Travis without the need to having PCAP related services available from > our CI. > Each file in the Fixture folder represents a response to a particular > request. This makes it fairly easy to create and maintain. > h3. How to run tests on your local machine > To run Cypress tests locally please do the following: > # pull this branch to your workspace > # move to metron-interface/metron-alerts folder > # run: npm ci > # run: scripts/start-server-for-e2e.sh > # run: node_modules/cypress/bin/cypress run > or run: node_modules/cypress/bin/cypress open > if you like to use the dashboard. > h3. Travis integration > As part of this PR I modified the package.json in metron-alert to make > Cypress running in Travis. If you like to see the integration working please > check to logs of build step [#3|https://github.com/apache/metron/pull/3]. > Failing Cypress tests brakes the build. > Example of build broken by failing Cypress test: > [https://travis-ci.com/tiborm/metron/builds/86869264] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] metron issue #1226: METRON-1803: Integrate Cypress with Travis
Github user tiborm commented on the issue: https://github.com/apache/metron/pull/1226 You are right @mmiklavc, this is an additional step to our build process. So it makes our build slightly slower. However, the two minutes come from the nature of PCAP. It has a built-in 10-second delay every time we check the job status. What makes these particular tests slower. With mocking out the time I was able to speed them up by 50%. I think it's also a good practice for the upcoming tests to keep them fast with this trick. ---
[jira] [Commented] (METRON-1815) Separate metron-parsers into metron-parsers-common and metron-parsers-storm
[ https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668681#comment-16668681 ] ASF GitHub Bot commented on METRON-1815: GitHub user justinleet opened a pull request: https://github.com/apache/metron/pull/1249 METRON-1815: Separate metron-parsers into metron-parsers-common and metron-parsers-storm ## Contributor Comments Separating metron-parsers into metron-parsers-common and metron-parsers-storm in order to decouple the parsers from Storm. This builds on the work from [METRON-1681](https://issues.apache.org/jira/browse/METRON-1681), done here: https://github.com/apache/metron/pull/1213. It looks like a ton of changes, but most of it is pretty minor naming adjustments, moving whole files, etc. Full dev should spin up and run exactly as it does prior to this PR, which is also how to test this. At this point, no org.apache.storm dependency should remain in metron-parsers-common (as that now lives in metron-parsers-storm). This means that we are typically going to be running, for now, off of metron-parsers-storm jars. Nothing changes in Ambari, because there's no actual second platform we're running on. In the future, I'd say we need to make some sort of configuration around this, but I'm fine with that being follow-on whenever we choose to build off of something other than Storm. This also adjusts some of the integration tests, so that it's easier to extend to a new platform once we add something beyond Storm. The current solution would involve a class for every parser for every platform, which seems awful. The new solution uses a parameterized test, and simply one extended class that's platform specific. Let me know thoughts on this and if we want to refactor this differently. The commit history is a little wonky, since this started based on his PR before it made it into master and there was a variety of merging happening there. The commits from @merrimanr are from that branch, not coauthored here. I'm a bit surprised git didn't handle it properly, but it won't matter once squashed. ## Pull Request Checklist Thank you for submitting a contribution to Apache Metron. Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions. Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides. In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel). - [x] Does your PR title start with METRON- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? ### For code changes: - [x] Have you included steps to reproduce the behavior or problem that is being changed or addressed? - [x] Have you included steps or a guide to how the change may be verified and tested manually? - [x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via: ``` mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh ``` - [x] Have you written or updated unit tests and or integration tests to verify your changes? - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`: ``` cd site-book mvn site ``` Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request. You can
[GitHub] metron pull request #1249: METRON-1815: Separate metron-parsers into metron-...
GitHub user justinleet opened a pull request: https://github.com/apache/metron/pull/1249 METRON-1815: Separate metron-parsers into metron-parsers-common and metron-parsers-storm ## Contributor Comments Separating metron-parsers into metron-parsers-common and metron-parsers-storm in order to decouple the parsers from Storm. This builds on the work from [METRON-1681](https://issues.apache.org/jira/browse/METRON-1681), done here: https://github.com/apache/metron/pull/1213. It looks like a ton of changes, but most of it is pretty minor naming adjustments, moving whole files, etc. Full dev should spin up and run exactly as it does prior to this PR, which is also how to test this. At this point, no org.apache.storm dependency should remain in metron-parsers-common (as that now lives in metron-parsers-storm). This means that we are typically going to be running, for now, off of metron-parsers-storm jars. Nothing changes in Ambari, because there's no actual second platform we're running on. In the future, I'd say we need to make some sort of configuration around this, but I'm fine with that being follow-on whenever we choose to build off of something other than Storm. This also adjusts some of the integration tests, so that it's easier to extend to a new platform once we add something beyond Storm. The current solution would involve a class for every parser for every platform, which seems awful. The new solution uses a parameterized test, and simply one extended class that's platform specific. Let me know thoughts on this and if we want to refactor this differently. The commit history is a little wonky, since this started based on his PR before it made it into master and there was a variety of merging happening there. The commits from @merrimanr are from that branch, not coauthored here. I'm a bit surprised git didn't handle it properly, but it won't matter once squashed. ## Pull Request Checklist Thank you for submitting a contribution to Apache Metron. Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions. Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides. In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel). - [x] Does your PR title start with METRON- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? ### For code changes: - [x] Have you included steps to reproduce the behavior or problem that is being changed or addressed? - [x] Have you included steps or a guide to how the change may be verified and tested manually? - [x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via: ``` mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh ``` - [x] Have you written or updated unit tests and or integration tests to verify your changes? - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`: ``` cd site-book mvn site ``` Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request. You can merge this pull request into a Git repository by running: $ git pull https://github.com/justinleet/metron parserSplit Alternatively you can review and apply these changes as the patch at:
[jira] [Commented] (METRON-1844) Allow for LDAP to be used for authentication and roles
[
https://issues.apache.org/jira/browse/METRON-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668665#comment-16668665
]
ASF GitHub Bot commented on METRON-1844:
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/1246#discussion_r229293771
--- Diff:
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/scripts/params/params_linux.py
---
@@ -267,6 +274,21 @@
if 'solr-config-env' in config['configurations']:
solr_principal_name = solr_principal_name.replace('_HOST',
hostname_lowercase)
+# LDAP
+metron_ldap_url =
config['configurations']['metron-security-env']['metron.ldap.url']
+metron_ldap_userdn =
config['configurations']['metron-security-env']['metron.ldap.bind.dn']
+metron_ldap_password =
config['configurations']['metron-security-env']['metron.ldap.bind.password']
+metron_ldap_user_pattern =
config['configurations']['metron-security-env']['metron.ldap.user.dnpattern']
+metron_ldap_user_password =
config['configurationsmetron_spring_profiles_active']['metron-security-env']['metron.ldap.user.password']
--- End diff --
Good catch. Fixed in latest commit
> 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)
[GitHub] metron pull request #1246: METRON-1844: Allow for LDAP to be used for authen...
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/1246#discussion_r229293771
--- Diff:
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/scripts/params/params_linux.py
---
@@ -267,6 +274,21 @@
if 'solr-config-env' in config['configurations']:
solr_principal_name = solr_principal_name.replace('_HOST',
hostname_lowercase)
+# LDAP
+metron_ldap_url =
config['configurations']['metron-security-env']['metron.ldap.url']
+metron_ldap_userdn =
config['configurations']['metron-security-env']['metron.ldap.bind.dn']
+metron_ldap_password =
config['configurations']['metron-security-env']['metron.ldap.bind.password']
+metron_ldap_user_pattern =
config['configurations']['metron-security-env']['metron.ldap.user.dnpattern']
+metron_ldap_user_password =
config['configurationsmetron_spring_profiles_active']['metron-security-env']['metron.ldap.user.password']
--- End diff --
Good catch. Fixed in latest commit
---
[jira] [Updated] (METRON-1848) Migrating Protractor E2E tests to Cypress
[ https://issues.apache.org/jira/browse/METRON-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Meller updated METRON-1848: - Description: *This ticket is made to track the migration of our protractor tests to cypress.* *The antecedent of this ticket is:* Add PCAP UI test implemented in Cypress.js https://issues.apache.org/jira/browse/METRON-1797 Integrate Cypress with Travis https://issues.apache.org/jira/browse/METRON-1803 *DISCUSSION thread:* [https://lists.apache.org/thread.html/b6a0272c7809c05e8b7aff20171720e8ec76f8a0e9481169c37a4a4a@%3Cdev.metron.apache.org%3E] *E2E Test Scenarios currently implemented with Protractor* *Alert details pane* (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) - Changing alert statuses - Adding comment for table view - Adding comment for tree view Scenarios to add: - Deleting comment *Filtering alerts* (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) - Display facets data - Search when facet is selected *Alert item status change on the list and tree view* (metron-alerts/e2e/alerts-list/alert-status/alerts-list-status.e2e-spec.ts) - change alert status for multiple alerts to OPEN - change alert status for multiple alerts to DISMISS - change alert status for multiple alerts to ESCALATE - change alert status for multiple alerts to RESOLVE - change alert status for multiple alerts to OPEN in tree view - change alert status for multiple alerts to DISMISS in tree view - change alert status for multiple alerts to ESCALATE in tree view - change alert status for multiple alerts to RESOLVE in tree view *Configure table view* (metron-alerts/e2e/alerts-list/configure-table/configure-table.e2e-spec.ts) - select columns from table configuration - rename columns from table configuration *Meta Alerts* (metron-alerts/e2e/alerts-list/meta-alerts/meta-alert.e2e-spec.ts) - should have all the steps for meta alerts workflow - should create a meta alert from nesting of more than one level - remove meta alerts *Search and save search* (metron-alerts/e2e/alerts-list/save-search/save-search.e2e-spec.ts) - should display all the default values for saved searches - should have all save search controls and they save search should be working - should delete search items from search box - should delete first search items from search box having multiple search fields - manually entering search queries to search box and pressing enter key should search *Alerts table view* (metron-alerts/e2e/alerts-list/table-view/table-view.e2e-spec.ts) - sorting ASC by ip_src_addr - sorting DESC by ip_src_addr - sorting ASC by Score - sorting DESC by Score *Alerts tree view* (metron-alerts/e2e/alerts-list/tree-view/tree-view.e2e-spec.ts) - should have all group by elements - drag and drop should change group order - should have group details for single group by - should have group details for multiple group by - should have sort working for group details for multiple sub groups - should have search working for group details for multiple sub groups *Alert list* (metron-alerts/e2e/alerts-list/alerts-list.e2e-spec.ts) - should have all the UI elements - should have all pagination controls and they should be working - should have all settings controls and they should be working - play pause should start polling and stop polling - should select columns from table configuration - should have all time-range controls - should have all time range values populated - 1 - should have all time range values populated - 2 - should have all time range values populated - 3 - should have all time range values populated - 4 - should disable date picker when timestamp is present in search - should have now included when to date is empty - should have all time-range included while searching *Login* (metron-alerts/e2e/login/login.e2e-spec.ts) - should display error message for invalid credentials - should login for valid credentials - should logout was: *This ticket is made to track the migration of our protractor tests to cypress.* *The antecedent of this ticket is:* *E2E Test Scenarios* *Alert details pane* (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) - Changing alert statuses - Adding comment for table view - Adding comment for tree view Scenarios to add: - Deleting comment *Filtering alerts* (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) - Display facets data - Search when facet is selected *Alert item status change on the list and tree view* (metron-alerts/e2e/alerts-list/alert-status/alerts-list-status.e2e-spec.ts) - change alert status for multiple alerts to OPEN - change alert status for multiple alerts to DISMISS - change alert status for multiple alerts to ESCALATE - change alert status for multiple alerts to RESOLVE - change alert status for
[jira] [Updated] (METRON-1848) Migrating Protractor E2E tests to Cypress
[ https://issues.apache.org/jira/browse/METRON-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Meller updated METRON-1848: - Description: *This ticket is made to track the migration of our protractor tests to cypress.* *The antecedent of this ticket is:* *E2E Test Scenarios* *Alert details pane* (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) - Changing alert statuses - Adding comment for table view - Adding comment for tree view Scenarios to add: - Deleting comment *Filtering alerts* (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) - Display facets data - Search when facet is selected *Alert item status change on the list and tree view* (metron-alerts/e2e/alerts-list/alert-status/alerts-list-status.e2e-spec.ts) - change alert status for multiple alerts to OPEN - change alert status for multiple alerts to DISMISS - change alert status for multiple alerts to ESCALATE - change alert status for multiple alerts to RESOLVE - change alert status for multiple alerts to OPEN in tree view - change alert status for multiple alerts to DISMISS in tree view - change alert status for multiple alerts to ESCALATE in tree view - change alert status for multiple alerts to RESOLVE in tree view *Configure table view* (metron-alerts/e2e/alerts-list/configure-table/configure-table.e2e-spec.ts) - select columns from table configuration - rename columns from table configuration *Meta Alerts* (metron-alerts/e2e/alerts-list/meta-alerts/meta-alert.e2e-spec.ts) - should have all the steps for meta alerts workflow - should create a meta alert from nesting of more than one level - remove meta alerts *Search and save search* (metron-alerts/e2e/alerts-list/save-search/save-search.e2e-spec.ts) - should display all the default values for saved searches - should have all save search controls and they save search should be working - should delete search items from search box - should delete first search items from search box having multiple search fields - manually entering search queries to search box and pressing enter key should search *Alerts table view* (metron-alerts/e2e/alerts-list/table-view/table-view.e2e-spec.ts) - sorting ASC by ip_src_addr - sorting DESC by ip_src_addr - sorting ASC by Score - sorting DESC by Score *Alerts tree view* (metron-alerts/e2e/alerts-list/tree-view/tree-view.e2e-spec.ts) - should have all group by elements - drag and drop should change group order - should have group details for single group by - should have group details for multiple group by - should have sort working for group details for multiple sub groups - should have search working for group details for multiple sub groups *Alert list* (metron-alerts/e2e/alerts-list/alerts-list.e2e-spec.ts) - should have all the UI elements - should have all pagination controls and they should be working - should have all settings controls and they should be working - play pause should start polling and stop polling - should select columns from table configuration - should have all time-range controls - should have all time range values populated - 1 - should have all time range values populated - 2 - should have all time range values populated - 3 - should have all time range values populated - 4 - should disable date picker when timestamp is present in search - should have now included when to date is empty - should have all time-range included while searching *Login* (metron-alerts/e2e/login/login.e2e-spec.ts) - should display error message for invalid credentials - should login for valid credentials - should logout was: *E2E Test Scenarios* *Alert details pane* (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) - Changing alert statuses - Adding comment for table view - Adding comment for tree view Scenarios to add: - Deleting comment *Filtering alerts* (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) - Display facets data - Search when facet is selected *Alert item status change on the list and tree view* (metron-alerts/e2e/alerts-list/alert-status/alerts-list-status.e2e-spec.ts) - change alert status for multiple alerts to OPEN - change alert status for multiple alerts to DISMISS - change alert status for multiple alerts to ESCALATE - change alert status for multiple alerts to RESOLVE - change alert status for multiple alerts to OPEN in tree view - change alert status for multiple alerts to DISMISS in tree view - change alert status for multiple alerts to ESCALATE in tree view - change alert status for multiple alerts to RESOLVE in tree view *Configure table view* (metron-alerts/e2e/alerts-list/configure-table/configure-table.e2e-spec.ts) - select columns from table configuration - rename columns from table configuration *Meta Alerts*
[jira] [Commented] (METRON-1844) Allow for LDAP to be used for authentication and roles
[
https://issues.apache.org/jira/browse/METRON-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668528#comment-16668528
]
ASF GitHub Bot commented on METRON-1844:
Github user anandsubbu commented on a diff in the pull request:
https://github.com/apache/metron/pull/1246#discussion_r229259363
--- Diff:
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/scripts/params/params_linux.py
---
@@ -267,6 +274,21 @@
if 'solr-config-env' in config['configurations']:
solr_principal_name = solr_principal_name.replace('_HOST',
hostname_lowercase)
+# LDAP
+metron_ldap_url =
config['configurations']['metron-security-env']['metron.ldap.url']
+metron_ldap_userdn =
config['configurations']['metron-security-env']['metron.ldap.bind.dn']
+metron_ldap_password =
config['configurations']['metron-security-env']['metron.ldap.bind.password']
+metron_ldap_user_pattern =
config['configurations']['metron-security-env']['metron.ldap.user.dnpattern']
+metron_ldap_user_password =
config['configurationsmetron_spring_profiles_active']['metron-security-env']['metron.ldap.user.password']
--- End diff --
Looks like a mispaste. `metron_spring_profiles_active` should be removed.
> 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)
[GitHub] metron pull request #1246: METRON-1844: Allow for LDAP to be used for authen...
Github user anandsubbu commented on a diff in the pull request:
https://github.com/apache/metron/pull/1246#discussion_r229259363
--- Diff:
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/scripts/params/params_linux.py
---
@@ -267,6 +274,21 @@
if 'solr-config-env' in config['configurations']:
solr_principal_name = solr_principal_name.replace('_HOST',
hostname_lowercase)
+# LDAP
+metron_ldap_url =
config['configurations']['metron-security-env']['metron.ldap.url']
+metron_ldap_userdn =
config['configurations']['metron-security-env']['metron.ldap.bind.dn']
+metron_ldap_password =
config['configurations']['metron-security-env']['metron.ldap.bind.password']
+metron_ldap_user_pattern =
config['configurations']['metron-security-env']['metron.ldap.user.dnpattern']
+metron_ldap_user_password =
config['configurationsmetron_spring_profiles_active']['metron-security-env']['metron.ldap.user.password']
--- End diff --
Looks like a mispaste. `metron_spring_profiles_active` should be removed.
---
