You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2017/10/25 19:03:01 UTC
[jira] [Resolved] (NIFIREG-44) Add integration tests for secure
NiFi Registry
[ https://issues.apache.org/jira/browse/NIFIREG-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Bende resolved NIFIREG-44.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.0.1
> Add integration tests for secure NiFi Registry
> ----------------------------------------------
>
> Key: NIFIREG-44
> URL: https://issues.apache.org/jira/browse/NIFIREG-44
> Project: NiFi Registry
> Issue Type: Test
> Reporter: Kevin Doran
> Assignee: Kevin Doran
> Fix For: 0.0.1
>
>
> Currently, the automated integration tests on master only run an unsecured NiFi Registry instance.
> This task is to add test suites that setup a secure connection between the client and the Registry.
> This will require a refactoring in order to prevent secure and non-secure configuration beans from ending up in the same application context. Instead of the \@RunWith and \@SpringBootTest annotations on the IntegrationBaseTest class, they will need to be moved to subclasses and configuration needs to by explicitly imported or limited to a profile active for that test suite.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)