[jira] [Updated] (NIFI-2321) Update Getting Started documentation for 1.0 changes
[ https://issues.apache.org/jira/browse/NIFI-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2321: - Fix Version/s: 1.0.0 > Update Getting Started documentation for 1.0 changes > > > Key: NIFI-2321 > URL: https://issues.apache.org/jira/browse/NIFI-2321 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Fix For: 1.0.0 > > > Getting Started guide needs to be updated for the changes in the 1.0 UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2265) Authorization: Able to see hidden processor information in Status History
Andrew Lim created NIFI-2265: Summary: Authorization: Able to see hidden processor information in Status History Key: NIFI-2265 URL: https://issues.apache.org/jira/browse/NIFI-2265 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.0.0 Reporter: Andrew Lim Attachments: NIFI-2265_statusHistory.png When a user is not privileged to see a processor, on the canvas the Name and Type of the Processor is properly hidden. But if you right-click on the processor and select "Stats", this information is displayed in the Status History. Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2265) Authorization: Able to see hidden processor information in Status History
[ https://issues.apache.org/jira/browse/NIFI-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2265: - Attachment: NIFI-2265_statusHistory.png > Authorization: Able to see hidden processor information in Status History > - > > Key: NIFI-2265 > URL: https://issues.apache.org/jira/browse/NIFI-2265 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Labels: UI > Attachments: NIFI-2265_statusHistory.png > > > When a user is not privileged to see a processor, on the canvas the Name and > Type of the Processor is properly hidden. But if you right-click on the > processor and select "Stats", this information is displayed in the Status > History. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2320) Update screenshot images in Getting Started guide for 1.0
[ https://issues.apache.org/jira/browse/NIFI-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15388168#comment-15388168 ] Andrew Lim commented on NIFI-2320: -- [~joewitt], I think this can be closed. I believe all screenshots with the older UI in the Getting Started guide have been updated as part of this Jira. > Update screenshot images in Getting Started guide for 1.0 > - > > Key: NIFI-2320 > URL: https://issues.apache.org/jira/browse/NIFI-2320 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Joseph Witt > Fix For: 1.0.0 > > > The screenshots in the documentation need to be updated for the new UI. > This ticket is for the images used or added to the Getting Started guide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1967) nifi.properties conversion for 1.0.0
[ https://issues.apache.org/jira/browse/NIFI-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-1967: - Affects Version/s: 1.0.0 > nifi.properties conversion for 1.0.0 > > > Key: NIFI-1967 > URL: https://issues.apache.org/jira/browse/NIFI-1967 > Project: Apache NiFi > Issue Type: Improvement > Components: Configuration, Documentation & Website >Affects Versions: 1.0.0 >Reporter: Matt Gilman >Assignee: Andrew Lim >Priority: Minor > Labels: migration > Fix For: 1.0.0 > > > With the properties changing it would be nice to offer an automated way of > converting an existing nifi.properties to the 1.0.0 version. Specifically, > the clustering properties have changed enough to warrant scripting this for > users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2420) Add a section for Multi-tenant Authorization to the Admin Guide
[ https://issues.apache.org/jira/browse/NIFI-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398625#comment-15398625 ] Andrew Lim commented on NIFI-2420: -- As part of this JIRA, will also include an update to the Admin guide with the new authorization system properties: -nifi.authorizer.configuration.file -nifi.security.user.authorizer > Add a section for Multi-tenant Authorization to the Admin Guide > --- > > Key: NIFI-2420 > URL: https://issues.apache.org/jira/browse/NIFI-2420 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Joseph Witt > Fix For: 1.0.0 > > Attachments: Multi-tenantAuthManage.pdf, Multi-tenantAuthSetup.pdf > > > Multi-tenant Authorization is a new feature in 1.0.0. A section covering > setup and management should be included in the documentation. > Attaching my first attempt at the doc in case anyone has any thoughts. > I plan to submit a PR soon depending on feedback and after more > editing/review on my part. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1969) Update Documentation for new Authorization Properties
[ https://issues.apache.org/jira/browse/NIFI-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398621#comment-15398621 ] Andrew Lim commented on NIFI-1969: -- [~joewitt], I agree this JIRA can be closed as a duplicate. I was aware of this ticket but thought of it as a minor update to add the 1.0 authorizer properties (nifi.authorizer.configuration.file, nifi.security.user.authorizer) to the System Properties list. I think it makes sense to add these properties with NIFI-2420 as part of a larger update to Admin for Multi-Tenant authorization. > Update Documentation for new Authorization Properties > - > > Key: NIFI-1969 > URL: https://issues.apache.org/jira/browse/NIFI-1969 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Mark Payne >Assignee: Andrew Lim >Priority: Critical > Labels: migration > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2420) Add a section for Multi-tenant Authorization to the Admin Guide
[ https://issues.apache.org/jira/browse/NIFI-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399558#comment-15399558 ] Andrew Lim commented on NIFI-2420: -- [~joewitt], thanks for reviewing those docs. I think the screenshots can be improved and will work on annotating them. Some things I think could be pointed out better: who the active user is in the screenshot and what resources that user has access to. I am also close to finishing a draft for the "User Identity Normalization" addition. Hoping to post a PR soon once those are done. > Add a section for Multi-tenant Authorization to the Admin Guide > --- > > Key: NIFI-2420 > URL: https://issues.apache.org/jira/browse/NIFI-2420 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Joseph Witt > Fix For: 1.0.0 > > Attachments: Multi-tenantAuthManage.pdf, Multi-tenantAuthSetup.pdf > > > Multi-tenant Authorization is a new feature in 1.0.0. A section covering > setup and management should be included in the documentation. > Attaching my first attempt at the doc in case anyone has any thoughts. > I plan to submit a PR soon depending on feedback and after more > editing/review on my part. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2420) Add a section for Multi-tenant Authorization to the Admin Guide
[ https://issues.apache.org/jira/browse/NIFI-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401341#comment-15401341 ] Andrew Lim commented on NIFI-2420: -- Thanks [~bende] for the feedback. Will add a section for the "brand new secure flow" scenario to the doc. > Add a section for Multi-tenant Authorization to the Admin Guide > --- > > Key: NIFI-2420 > URL: https://issues.apache.org/jira/browse/NIFI-2420 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > Attachments: Multi-tenantAuthManage.pdf, Multi-tenantAuthSetup.pdf > > > Multi-tenant Authorization is a new feature in 1.0.0. A section covering > setup and management should be included in the documentation. > Attaching my first attempt at the doc in case anyone has any thoughts. > I plan to submit a PR soon depending on feedback and after more > editing/review on my part. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2451) Need to update Encryption Configuration in Admin Guide for 1.0 changes
Andrew Lim created NIFI-2451: Summary: Need to update Encryption Configuration in Admin Guide for 1.0 changes Key: NIFI-2451 URL: https://issues.apache.org/jira/browse/NIFI-2451 Project: Apache NiFi Issue Type: Bug Components: Documentation & Website Affects Versions: 1.0.0 Reporter: Andrew Lim Assignee: Andrew Lim Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2451) Need to update Encryption Configuration in Admin Guide for 1.0 changes
[ https://issues.apache.org/jira/browse/NIFI-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2451: - Description: Will need to document changes being made in NIFI-1831 > Need to update Encryption Configuration in Admin Guide for 1.0 changes > -- > > Key: NIFI-2451 > URL: https://issues.apache.org/jira/browse/NIFI-2451 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Will need to document changes being made in NIFI-1831 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2451) Need to update Encryption Configuration content in Admin guide for 1.0 changes
[ https://issues.apache.org/jira/browse/NIFI-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2451: - Summary: Need to update Encryption Configuration content in Admin guide for 1.0 changes (was: Need to update Encryption Configuration content in for 1.0 changes) > Need to update Encryption Configuration content in Admin guide for 1.0 changes > -- > > Key: NIFI-2451 > URL: https://issues.apache.org/jira/browse/NIFI-2451 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Will need to document changes in Admin Guide for: > NIFI-1831 for Encryption Configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2449) Need to document Variable Registry work in 1.0
[ https://issues.apache.org/jira/browse/NIFI-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417296#comment-15417296 ] Andrew Lim commented on NIFI-2449: -- First draft of content to add to Getting Started guide after “Working with Attributes” section: Custom Properties within Expression Language In addition to using FlowFile attributes, you can also define custom properties for Expression Language use. Defining custom properties gives you additional flexibility in processing and configuring dataflows. For example, you can refer to custom properties for connection, server, and service properties. When you define custom properties, ensure that the following criteria are met: -Each custom property contains a distinct property value, so that it is not overridden by existing environment properties, system properties, or FlowFile attributes. -Each node in a clustered environment is configured with the same custom properties. Once you have created custom properties, you can identify their location in the nifi.variable.registry.properties field in the nifi.properties file. After you have updated the nifi.properties file and restarted NiFi, you are able to use custom properties as needed. > Need to document Variable Registry work in 1.0 > -- > > Key: NIFI-2449 > URL: https://issues.apache.org/jira/browse/NIFI-2449 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Need to capture work done in NIFI-2208. Admin and Getting Started guides > should be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2449) Need to document Variable Registry work in 1.0
[ https://issues.apache.org/jira/browse/NIFI-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418286#comment-15418286 ] Andrew Lim commented on NIFI-2449: -- Trimming Getting Started content to make it more of a brief intro to custom properties. Admin Guide will contain info about creation and configuration. NIFI-2556 will cover info needed from a user's perspective. Getting Started: Custom Properties within Expression Language In addition to using FlowFile attributes, you can also define custom properties for Expression Language use. Defining custom properties gives you additional flexibility in processing and configuring dataflows. For example, you can refer to custom properties for connection, server, and service properties. Once you have created custom properties, you can identify their location in the nifi.variable.registry.properties field in the nifi.properties file. After you have updated the nifi.properties file and restarted NiFi, you are able to use custom properties as needed. Admin Guide: Custom Properties To configure custom properties for use with NiFi’s Expression Language: -Create the custom property. Ensure that: --Each custom property contains a distinct property value, so that it is not overridden by existing environment properties, system properties, or FlowFile attributes. --Each node in a clustered environment is configured with the same custom properties. -Update the nifi.properties file with the location of the custom property files. Property Description nifi.variable.registry.propertiesThis is a comma-separated list of location paths for one or more custom property files. > Need to document Variable Registry work in 1.0 > -- > > Key: NIFI-2449 > URL: https://issues.apache.org/jira/browse/NIFI-2449 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Need to capture work done in NIFI-2208. Admin and Getting Started guides > should be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-2541) Update Multi-tenant authorization doc for UI change to Policy page
[ https://issues.apache.org/jira/browse/NIFI-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-2541: Assignee: Andrew Lim > Update Multi-tenant authorization doc for UI change to Policy page > -- > > Key: NIFI-2541 > URL: https://issues.apache.org/jira/browse/NIFI-2541 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > Fix For: 1.0.0 > > > Updating doc for NIFI-2475. Want to make it clear to user that view/modify > policies do not support inheritance override. > Will add to end of Access Policy Inheritance section: > Note: “View the policies” and “modify the policies” component-level access > policies are an exception to this inherited behavior. When a user is added > to either policy, they are added to the current list of administrators. They > do not override higher level administrators. For this reason, only component > specific administrators are displayed for the “view the policies” and “modify > the policies" access policies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2541) Update Multi-tenant authorization doc for UI change to Policy page
Andrew Lim created NIFI-2541: Summary: Update Multi-tenant authorization doc for UI change to Policy page Key: NIFI-2541 URL: https://issues.apache.org/jira/browse/NIFI-2541 Project: Apache NiFi Issue Type: Improvement Components: Documentation & Website Affects Versions: 1.0.0 Reporter: Andrew Lim Priority: Minor Fix For: 1.0.0 Updating doc for NIFI-2475. Want to make it clear to user that view/modify policies do not support inheritance override. Will add to end of Access Policy Inheritance section: Note: “View the policies” and “modify the policies” component-level access policies are an exception to this inherited behavior. When a user is added to either policy, they are added to the current list of administrators. They do not override higher level administrators. For this reason, only component specific administrators are displayed for the “view the policies” and “modify the policies" access policies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2449) Need to document Variable Registry work in 1.0
[ https://issues.apache.org/jira/browse/NIFI-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2449: - Description: Need to capture work done in NIFI-2208. Admin and Getting Started guides should be updated. (was: Need to capture work done in NIFI-2208. Admin and User Guides should be updated.) > Need to document Variable Registry work in 1.0 > -- > > Key: NIFI-2449 > URL: https://issues.apache.org/jira/browse/NIFI-2449 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Need to capture work done in NIFI-2208. Admin and Getting Started guides > should be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2451) Need to update Encryption Configuration content in Admin guide for 1.0 changes
[ https://issues.apache.org/jira/browse/NIFI-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419785#comment-15419785 ] Andrew Lim commented on NIFI-2451: -- Will add the following to Admin Guide after Encryption Configuration: Encrypted Passwords in Configuration Files In order to facilitate the secure setup of NiFi, you can use the encrypt-config command line utility to encrypt raw configuration values that NiFi decrypts in memory on startup. This extensible protection scheme transparently allows NiFi to use raw values in operation, while protecting them at rest. In the future, hardware security modules (HSM) and external secure storage mechanisms will be integrated, but for now, an AES encryption provider is the default implementation. This is a change in behavior; prior to 1.0, all configuration values were stored in plaintext on the file system. POSIX file permissions were recommended to limit unauthorized access to these files If no administrator action is taken, the configuration values remain unencrypted. Encrypt-Config Tool The encrypt-config command line tool reads from a nifi.properties file with plaintext sensitive configuration values, prompts you for a master key, and encrypts each value. It replaces the plain values with the protected value in the same file, or writes to a new nifi.properties file if specified. The default encryption algorithm utilized is AES/GCM 128/256-bit. 128-bit is used if JCE Unlimited Strength Crypto Policy is not installed, and 256-bit is used if it is installed. You can use the following command line options with the encrypt-config tool: -b (or --bootstrapConf) Specifies the bootstrap.conf file you want to use to persist the master key. -h (or --help) Prints this usage message. -k (or --hexKey) The raw hexadecimal key to use to encrypt the sensitive properties. Must be a 32 or 64 hexadecimal string. Some basic error handling is performed if the string is not formatted properly. -n (or --niFiProperties) The nifi.properties file containing unprotected config values. The input nifi.properties file is overwritten. -o (or --outputNiFiProperties) The destination nifi.properties file containing protected config values. The input nifi.properties file is not modified. As an example of how the tool works, assume that you have installed the tool on a machine supporting 256-bit encryption and with following existing values in the nifi.properties file: # security properties # nifi.sensitive.props.key=thisIsABadSensitiveKeyPassword nifi.sensitive.props.algorithm=PBEWITHMD5AND256BITAES-CBC-OPENSSL nifi.sensitive.props.provider=BC nifi.sensitive.props.additional.keys= nifi.security.keystore=/path/to/keystore.jks nifi.security.keystoreType=JKS nifi.security.keystorePasswd=thisIsABadKeystorePassword nifi.security.keyPasswd=thisIsABadKeyPassword nifi.security.truststore= nifi.security.truststoreType= nifi.security.truststorePasswd= Enter the following arguments when using the tool: encrypt-config.sh -b bootstrap.conf -k 0123456789ABCDEFFEDCBA98765432100123456789ABCDEFFEDCBA9876543210 -n nifi.properties As a result, the nifi.properties file is overwritten with protected properties and sibling encryption identifiers (aes/gcm/256, the currently supported algorithm): # security properties # nifi.sensitive.props.key=n2z+tTTbHuZ4V4V2||uWhdasyDXD4ZG2lMAes/vqh6u4vaz4xgL4aEbF4Y/dXevqk3ulRcOwf1vc4RDQ== nifi.sensitive.props.key.protected=aes/gcm/256 nifi.sensitive.props.algorithm=PBEWITHMD5AND256BITAES-CBC-OPENSSL nifi.sensitive.props.provider=BC nifi.sensitive.props.additional.keys= nifi.security.keystore=/path/to/keystore.jks nifi.security.keystoreType=JKS nifi.security.keystorePasswd=oBjT92hIGRElIGOh||MZ6uYuWNBrOA6usq/Jt3DaD2e4otNirZDytac/w/KFe0HOkrJR03vcbo nifi.security.keystorePasswd.protected=aes/gcm/256 nifi.security.keyPasswd=ac/BaE35SL/esLiJ||+ULRvRLYdIDA2VqpE0eQXDEMjaLBMG2kbKOdOwBk/hGebDKlVg== nifi.security.keyPasswd.protected=aes/gcm/256 nifi.security.truststore= nifi.security.truststoreType= nifi.security.truststorePasswd= Additionally, the bootstrap.conf file is updated with the encryption key as follows: # Master key in hexadecimal format for encrypted sensitive configuration values nifi.bootstrap.sensitive.key=0123456789ABCDEFFEDCBA98765432100123456789ABCDEFFEDCBA9876543210 Sensitive configuration values are encrypted by the tool by default, however you can encrypt any additional properties, if desired. To encrypt additional properties, specify them as comma-separated values in the nifi.sensitive.props.additional.keys property. If the nifi.properties file already has valid protected values, those property values are not modified by the tool. > Need to update Encryption Configuration content in Admin guide for 1.0 changes > -- > > Key: NIFI-2451 >
[jira] [Updated] (NIFI-2320) Update screenshot images in Getting Started guide for 1.0
[ https://issues.apache.org/jira/browse/NIFI-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2320: - Fix Version/s: 1.0.0 > Update screenshot images in Getting Started guide for 1.0 > - > > Key: NIFI-2320 > URL: https://issues.apache.org/jira/browse/NIFI-2320 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Fix For: 1.0.0 > > > The screenshots in the documentation need to be updated for the new UI. > This ticket is for the images used or added to the Getting Started guide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2294) Scroll bar exists in the Settings tab of the Configure Connection window
[ https://issues.apache.org/jira/browse/NIFI-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2294: - Attachment: NIFI-2294_scrollBar.png > Scroll bar exists in the Settings tab of the Configure Connection window > > > Key: NIFI-2294 > URL: https://issues.apache.org/jira/browse/NIFI-2294 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Affects Versions: 1.0.0 > Environment: Mac OS X, Chrome >Reporter: Andrew Lim >Priority: Minor > Labels: UI > Attachments: NIFI-2294_scrollBar.png > > > The existence of a scroll bar in this window is inconsistent with the rest of > the application and also doesn't seem necessary. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2282) Purge history not working
[ https://issues.apache.org/jira/browse/NIFI-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15382967#comment-15382967 ] Andrew Lim commented on NIFI-2282: -- I was having issues to even get the Purge History window to open, but that was in an older build. Using a more recent build, I can confirm that Purge History is working as expected so this bug can be closed out. > Purge history not working > - > > Key: NIFI-2282 > URL: https://issues.apache.org/jira/browse/NIFI-2282 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Rob Moran > > Tried to purge config history from Flow Configuration History shell. The > purge operation is captured and displayed in the table, but previous > operations are not removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2321) Update Getting Started documentation for 1.0 changes
Andrew Lim created NIFI-2321: Summary: Update Getting Started documentation for 1.0 changes Key: NIFI-2321 URL: https://issues.apache.org/jira/browse/NIFI-2321 Project: Apache NiFi Issue Type: Bug Components: Documentation & Website Affects Versions: 1.0.0 Reporter: Andrew Lim Getting Started guide needs to be updated for the changes in the 1.0 UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2329) User authorization: Able to create a user with the same name which causes that user to lose User & Policies privileges
[ https://issues.apache.org/jira/browse/NIFI-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2329: - Summary: User authorization: Able to create a user with the same name which causes that user to lose User & Policies privileges (was: User authorization: Able to create a users with the same name which causes that user to lose User & Policies privileges) > User authorization: Able to create a user with the same name which causes > that user to lose User & Policies privileges > --- > > Key: NIFI-2329 > URL: https://issues.apache.org/jira/browse/NIFI-2329 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Critical > > I had an initial admin user who had default privs to access and modify Users > & Policies. The UI allowed me to create another user with the same name. > After that, the user could no longer access Users (get the error "Unable to > perform the desired action due to insufficient permissions. Contact the > system administrator.") and can get into the Policies window, but can no > longer make changes and see the message "Not authorized to access the policy > for the specified resource." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2329) User authorization: Able to create a users with the same name which causes that user to lose User & Policies privileges
[ https://issues.apache.org/jira/browse/NIFI-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2329: - Description: I had an initial admin user who had default privs to access and modify Users & Policies. The UI allowed me to create another user with the same name. After that, the user could no longer access Users (get the error "Unable to perform the desired action due to insufficient permissions. Contact the system administrator.") and can get into the Policies window, but can no longer make changes and see the message "Not authorized to access the policy for the specified resource." was: I had an initial admin user who had default privs to access and modify Users & Policies. The UI allowed me to create another user with the same name. After that, the user could no longer access Users (get the error "Unable to perform the desired action due to insufficient permissions. Contact the system administrator." and can get into the Policies window, but can no longer make changes and see the message "Not authorized to access the policy for the specified resource." > User authorization: Able to create a users with the same name which causes > that user to lose User & Policies privileges > > > Key: NIFI-2329 > URL: https://issues.apache.org/jira/browse/NIFI-2329 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Critical > > I had an initial admin user who had default privs to access and modify Users > & Policies. The UI allowed me to create another user with the same name. > After that, the user could no longer access Users (get the error "Unable to > perform the desired action due to insufficient permissions. Contact the > system administrator.") and can get into the Policies window, but can no > longer make changes and see the message "Not authorized to access the policy > for the specified resource." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2329) User authorization: Able to create a users with the same name which causes that user to lose User & Policies privileges
Andrew Lim created NIFI-2329: Summary: User authorization: Able to create a users with the same name which causes that user to lose User & Policies privileges Key: NIFI-2329 URL: https://issues.apache.org/jira/browse/NIFI-2329 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.0.0 Reporter: Andrew Lim Priority: Critical I had an initial admin user who had default privs to access and modify Users & Policies. The UI allowed me to create another user with the same name. After that, the user could no longer access Users (get the error "Unable to perform the desired action due to insufficient permissions. Contact the system administrator." and can get into the Policies window, but can no longer make changes and see the message "Not authorized to access the policy for the specified resource." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2320) Update screenshot images in Getting Started guide
Andrew Lim created NIFI-2320: Summary: Update screenshot images in Getting Started guide Key: NIFI-2320 URL: https://issues.apache.org/jira/browse/NIFI-2320 Project: Apache NiFi Issue Type: Bug Components: Documentation & Website Affects Versions: 1.0.0 Reporter: Andrew Lim The screenshots in the documentation need to be updated for the new UI. This ticket will cover the images used or added to the Getting Started guide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2320) Update screenshot images in Getting Started guide
[ https://issues.apache.org/jira/browse/NIFI-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2320: - Description: The screenshots in the documentation need to be updated for the new UI. This ticket is for the images used or added to the Getting Started guide. was: The screenshots in the documentation need to be updated for the new UI. This ticket will cover the images used or added to the Getting Started guide. > Update screenshot images in Getting Started guide > - > > Key: NIFI-2320 > URL: https://issues.apache.org/jira/browse/NIFI-2320 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > > The screenshots in the documentation need to be updated for the new UI. > This ticket is for the images used or added to the Getting Started guide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-2320) Update screenshot images in Getting Started guide
[ https://issues.apache.org/jira/browse/NIFI-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-2320: Assignee: Andrew Lim > Update screenshot images in Getting Started guide > - > > Key: NIFI-2320 > URL: https://issues.apache.org/jira/browse/NIFI-2320 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > > The screenshots in the documentation need to be updated for the new UI. > This ticket will cover the images used or added to the Getting Started guide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2331) Authorization: Adding a user and then deleting that user causes and error and also removes privileges to Users & Policies
Andrew Lim created NIFI-2331: Summary: Authorization: Adding a user and then deleting that user causes and error and also removes privileges to Users & Policies Key: NIFI-2331 URL: https://issues.apache.org/jira/browse/NIFI-2331 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.0.0 Reporter: Andrew Lim Login to system as the Initial Admin User. This user has default read & write privs to Users & Policies. Add a new user. Then attempt to delete that user. This results in an error "Unable to perform the desired action due to insufficient permissions. Contact the system administrator." even though this should be allowed. If you return to main UI, the initial admin user now cannot access User and Policies menu items. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2288) Authorization: Start and Stop buttons in Operate pallette are active for a user that only has view privileges to process group
Andrew Lim created NIFI-2288: Summary: Authorization: Start and Stop buttons in Operate pallette are active for a user that only has view privileges to process group Key: NIFI-2288 URL: https://issues.apache.org/jira/browse/NIFI-2288 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.0.0 Reporter: Andrew Lim Priority: Minor A user only has view privileges to a process group, however the Start and Stop buttons in the Operate pallete are active and clickable, when they should be inactive. Clicking the Start and Stop buttons doesn't do anything, which is why I marked as Minor priority, but this is still confusing to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2288) Authorization: Start and Stop buttons in Operate pallette are active for a user that only has view privileges to process group
[ https://issues.apache.org/jira/browse/NIFI-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2288: - Description: A non-administrator user only has view privileges to a process group, however the Start and Stop buttons in the Operate pallete are active and clickable, when they should be inactive. Clicking the Start and Stop buttons doesn't do anything, which is why I marked as Minor priority, but this is still confusing to the user. was: A user only has view privileges to a process group, however the Start and Stop buttons in the Operate pallete are active and clickable, when they should be inactive. Clicking the Start and Stop buttons doesn't do anything, which is why I marked as Minor priority, but this is still confusing to the user. > Authorization: Start and Stop buttons in Operate pallette are active for a > user that only has view privileges to process group > --- > > Key: NIFI-2288 > URL: https://issues.apache.org/jira/browse/NIFI-2288 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Labels: UI > > A non-administrator user only has view privileges to a process group, however > the Start and Stop buttons in the Operate pallete are active and clickable, > when they should be inactive. > Clicking the Start and Stop buttons doesn't do anything, which is why I > marked as Minor priority, but this is still confusing to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1846) Build requires Git through Bower
[ https://issues.apache.org/jira/browse/NIFI-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-1846: - Component/s: Documentation & Website > Build requires Git through Bower > > > Key: NIFI-1846 > URL: https://issues.apache.org/jira/browse/NIFI-1846 > Project: Apache NiFi > Issue Type: Task > Components: Documentation & Website, Tools and Build >Reporter: Matt Gilman >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Investigate build to see if there is an alternative which would not introduce > new requirements in our process build. If unable to remove dependency, need > to update the getting started/contribution/release helper to indicate that > Git is required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1846) Build requires Git through Bower
[ https://issues.apache.org/jira/browse/NIFI-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-1846: - Assignee: Andrew Lim > Build requires Git through Bower > > > Key: NIFI-1846 > URL: https://issues.apache.org/jira/browse/NIFI-1846 > Project: Apache NiFi > Issue Type: Task > Components: Documentation & Website, Tools and Build >Reporter: Matt Gilman >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Investigate build to see if there is an alternative which would not introduce > new requirements in our process build. If unable to remove dependency, need > to update the getting started/contribution/release helper to indicate that > Git is required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2114) In content viewer window, view as 'formatted' has no effect on the display of text
[ https://issues.apache.org/jira/browse/NIFI-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2114: - Fix Version/s: (was: 1.0.0) > In content viewer window, view as 'formatted' has no effect on the display of > text > -- > > Key: NIFI-2114 > URL: https://issues.apache.org/jira/browse/NIFI-2114 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Labels: UI > Attachments: NIFI-2114_viewAs.png > > > New styling hasn't been applied to this window yet > (https://issues.apache.org/jira/browse/NIFI-2107), but noticed that when user > chooses "View as formatted", the display of the text remains unchanged from > the default selection of 'original'. Selecting 'hex' works. > See attached screenshot for JSON text. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2273) Policies: Get an "Unable to perform the desired action due to insufficient permissions. Contact the system administrator." error trying to access the policies of a compon
Andrew Lim created NIFI-2273: Summary: Policies: Get an "Unable to perform the desired action due to insufficient permissions. Contact the system administrator." error trying to access the policies of a component Key: NIFI-2273 URL: https://issues.apache.org/jira/browse/NIFI-2273 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.0.0 Reporter: Andrew Lim User does not have a policy to view a processor. However, when the processor is selected and "Policies" is selected from the Operator palette, an error box is displayed with the following message: Unable to perform the desired action due to insufficient permissions. Contact the system administrator. The Policies window should still be displayed/accessible for the user to be able to make policy changes. Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2272) Policies: The view/modify drop-down should not be displayed for the "access the user interface" policy
[ https://issues.apache.org/jira/browse/NIFI-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2272: - Attachment: NIFI-2272_viewModify.png > Policies: The view/modify drop-down should not be displayed for the "access > the user interface" policy > --- > > Key: NIFI-2272 > URL: https://issues.apache.org/jira/browse/NIFI-2272 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Labels: UI > Attachments: NIFI-2272_viewModify.png > > > I reloaded my NiFi instance and selected "Profiles" from the control > drop-down menu. As shown in the attached screenshot, for the "access the > user interface" policy, the view/modify drop-down is available. > If you switch to another policy like "query provenance" which correctly > doesn't have the view/modify drop-down, then if you go back to "access the > user interface" policy the view/modify drop-down is now gone. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2265) Authorization: Able to see hidden processor information in Status History
[ https://issues.apache.org/jira/browse/NIFI-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2265: - Attachment: NIFI-2265_Summary.png > Authorization: Able to see hidden processor information in Status History > - > > Key: NIFI-2265 > URL: https://issues.apache.org/jira/browse/NIFI-2265 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Labels: UI > Attachments: NIFI-2265_Summary.png, NIFI-2265_statusHistory.png > > > When a user is not privileged to see a processor, on the canvas the Name and > Type of the Processor is properly hidden. But if you right-click on the > processor and select "Stats", this information is displayed in the Status > History. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2272) Policies: The view/modify drop-down should not be displayed for the "access the user interface" policy
[ https://issues.apache.org/jira/browse/NIFI-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2272: - Description: I reloaded my NiFi instance and selected "Policies" from the control drop-down menu. As shown in the attached screenshot, for the "access the user interface" policy, the view/modify drop-down is available. If you switch to another policy like "query provenance" which correctly doesn't have the view/modify drop-down, then if you go back to "access the user interface" policy the view/modify drop-down is now gone. The UI is also corrected if you close the Access Policies window and then open it again. was: I reloaded my NiFi instance and selected "Policies" from the control drop-down menu. As shown in the attached screenshot, for the "access the user interface" policy, the view/modify drop-down is available. If you switch to another policy like "query provenance" which correctly doesn't have the view/modify drop-down, then if you go back to "access the user interface" policy the view/modify drop-down is now gone. > Policies: The view/modify drop-down should not be displayed for the "access > the user interface" policy > --- > > Key: NIFI-2272 > URL: https://issues.apache.org/jira/browse/NIFI-2272 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Labels: UI > Attachments: NIFI-2272_viewModify.png > > > I reloaded my NiFi instance and selected "Policies" from the control > drop-down menu. As shown in the attached screenshot, for the "access the > user interface" policy, the view/modify drop-down is available. > If you switch to another policy like "query provenance" which correctly > doesn't have the view/modify drop-down, then if you go back to "access the > user interface" policy the view/modify drop-down is now gone. The UI is also > corrected if you close the Access Policies window and then open it again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2273) Policies: Get an "Unable to perform the desired action due to insufficient permissions. Contact the system administrator." error trying to access the policies of a compon
[ https://issues.apache.org/jira/browse/NIFI-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2273: - Attachment: NIFI-2273_componentError.png > Policies: Get an "Unable to perform the desired action due to insufficient > permissions. Contact the system administrator." error trying to access the > policies of a component > -- > > Key: NIFI-2273 > URL: https://issues.apache.org/jira/browse/NIFI-2273 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Labels: UI > Attachments: NIFI-2273_componentError.png > > > User does not have a policy to view a processor. However, when the processor > is selected and "Policies" is selected from the Operator palette, an error > box is displayed with the following message: > Unable to perform the desired action due to insufficient permissions. Contact > the system administrator. > The Policies window should still be displayed/accessible for the user to be > able to make policy changes. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1991) Zero Master Cluster: Modifying a disconnected node causes other nodes to not be able to join cluster
[ https://issues.apache.org/jira/browse/NIFI-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373267#comment-15373267 ] Andrew Lim commented on NIFI-1991: -- Thanks for the comments [~markap14]. Moving to 1.1.0. > Zero Master Cluster: Modifying a disconnected node causes other nodes to not > be able to join cluster > - > > Key: NIFI-1991 > URL: https://issues.apache.org/jira/browse/NIFI-1991 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Andrew Lim >Priority: Blocker > Fix For: 1.1.0 > > > I created a zero master cluster with 3 nodes. All three were up and running. > I stopped all 3 instances and then brought up just Node1. > In the Node1 UI, I made some edits to the flow. > I attempted but was not able to bring up Node2 and Node3 to join the cluster. > Here is what I saw in the logs: > 2016-06-09 14:35:47,051 WARN [main] org.apache.nifi.web.server.JettyServer > Failed to start web server... shutting down. > java.lang.Exception: Unable to load flow due to: java.io.IOException: > org.apache.nifi.controller.UninheritableFlowException: Failed to connect node > to cluster because local flow is different than cluster flow. > at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:753) > ~[nifi-jetty-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.apache.nifi.NiFi.(NiFi.java:137) > [nifi-runtime-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.apache.nifi.NiFi.main(NiFi.java:227) > [nifi-runtime-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > Caused by: java.io.IOException: > org.apache.nifi.controller.UninheritableFlowException: Failed to connect node > to cluster because local flow is different than cluster flow. > at > org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:501) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:744) > ~[nifi-jetty-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > ... 2 common frames omitted > Caused by: org.apache.nifi.controller.UninheritableFlowException: Failed to > connect node to cluster because local flow is different than cluster flow. > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:862) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at > org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:497) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > ... 3 common frames omitted > Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed > configuration is not inheritable by the flow controller because of flow > differences: Found difference in Flows: > Local Fingerprint contains additional configuration from Cluster Fingerprint: > eba77dac-32ad-356b-8a82-f669d046aa21eba77dac-32ad-356b-8a82-f669d046aa21org.apache.nifi.processors.standard.LogAttributeNO_VALUEAttributes > to IgnoreNO_VALUEAttributes to LogNO_VALUELog prefixNO_VALUEs > at > org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:219) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at > org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1329) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at > org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:75) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at > org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:668) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:839) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > ... 4 common frames omitted > 2016-06-09 14:35:47,052 INFO [Thread-1] org.apache.nifi.NiFi Initiating > shutdown of Jetty web server... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1991) Zero Master Cluster: Modifying a disconnected node causes other nodes to not be able to join cluster
[ https://issues.apache.org/jira/browse/NIFI-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-1991: - Fix Version/s: (was: 1.0.0) 1.1.0 > Zero Master Cluster: Modifying a disconnected node causes other nodes to not > be able to join cluster > - > > Key: NIFI-1991 > URL: https://issues.apache.org/jira/browse/NIFI-1991 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Andrew Lim >Priority: Blocker > Fix For: 1.1.0 > > > I created a zero master cluster with 3 nodes. All three were up and running. > I stopped all 3 instances and then brought up just Node1. > In the Node1 UI, I made some edits to the flow. > I attempted but was not able to bring up Node2 and Node3 to join the cluster. > Here is what I saw in the logs: > 2016-06-09 14:35:47,051 WARN [main] org.apache.nifi.web.server.JettyServer > Failed to start web server... shutting down. > java.lang.Exception: Unable to load flow due to: java.io.IOException: > org.apache.nifi.controller.UninheritableFlowException: Failed to connect node > to cluster because local flow is different than cluster flow. > at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:753) > ~[nifi-jetty-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.apache.nifi.NiFi.(NiFi.java:137) > [nifi-runtime-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.apache.nifi.NiFi.main(NiFi.java:227) > [nifi-runtime-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > Caused by: java.io.IOException: > org.apache.nifi.controller.UninheritableFlowException: Failed to connect node > to cluster because local flow is different than cluster flow. > at > org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:501) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:744) > ~[nifi-jetty-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > ... 2 common frames omitted > Caused by: org.apache.nifi.controller.UninheritableFlowException: Failed to > connect node to cluster because local flow is different than cluster flow. > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:862) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at > org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:497) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > ... 3 common frames omitted > Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed > configuration is not inheritable by the flow controller because of flow > differences: Found difference in Flows: > Local Fingerprint contains additional configuration from Cluster Fingerprint: > eba77dac-32ad-356b-8a82-f669d046aa21eba77dac-32ad-356b-8a82-f669d046aa21org.apache.nifi.processors.standard.LogAttributeNO_VALUEAttributes > to IgnoreNO_VALUEAttributes to LogNO_VALUELog prefixNO_VALUEs > at > org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:219) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at > org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1329) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at > org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:75) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at > org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:668) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:839) > ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > ... 4 common frames omitted > 2016-06-09 14:35:47,052 INFO [Thread-1] org.apache.nifi.NiFi Initiating > shutdown of Jetty web server... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2296) The hover text for the Search icon in the Upload Template window is confusing
Andrew Lim created NIFI-2296: Summary: The hover text for the Search icon in the Upload Template window is confusing Key: NIFI-2296 URL: https://issues.apache.org/jira/browse/NIFI-2296 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Affects Versions: 1.0.0 Reporter: Andrew Lim Priority: Minor When the user hovers over the Search icon in the Upload Template window, the text displayed is either "No file chosen" or the name of the template xml chosen. This text doesn't aide the user in determining what the icon/button is for and also displays redundant information when a template has been selected. See attached screenshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2296) The hover text for the Search icon in the Upload Template window is confusing
[ https://issues.apache.org/jira/browse/NIFI-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2296: - Attachment: NIFI-2296_xmlChosen.png NIFI-2296_noFileChosen.png > The hover text for the Search icon in the Upload Template window is confusing > - > > Key: NIFI-2296 > URL: https://issues.apache.org/jira/browse/NIFI-2296 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Labels: UI > Attachments: NIFI-2296_noFileChosen.png, NIFI-2296_xmlChosen.png > > > When the user hovers over the Search icon in the Upload Template window, the > text displayed is either "No file chosen" or the name of the template xml > chosen. This text doesn't aide the user in determining what the icon/button > is for and also displays redundant information when a template has been > selected. See attached screenshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2286) Policies: "Add user to policy" and "Remove" icons do not have hover help text
[ https://issues.apache.org/jira/browse/NIFI-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2286: - Description: After creating a policy, the "Add user to policy" and "Remove" icons become active. If the user hovers over these buttons there is no help text provided. This will be really helpful especially to new users of the Authorization API. was: After creating a policy, the "Add user to policy" and "Remove" icons become active. If the user hovers over these buttons there is no help text provided. This will be really helpful especially with new users of the Authorization API. > Policies: "Add user to policy" and "Remove" icons do not have hover help text > -- > > Key: NIFI-2286 > URL: https://issues.apache.org/jira/browse/NIFI-2286 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.1.0 >Reporter: Andrew Lim >Priority: Minor > Labels: UI > > After creating a policy, the "Add user to policy" and "Remove" icons become > active. If the user hovers over these buttons there is no help text provided. > This will be really helpful especially to new users of the Authorization API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2502) Update Multi-tenant Authorization section in Admin Guide for recent changes
Andrew Lim created NIFI-2502: Summary: Update Multi-tenant Authorization section in Admin Guide for recent changes Key: NIFI-2502 URL: https://issues.apache.org/jira/browse/NIFI-2502 Project: Apache NiFi Issue Type: Improvement Components: Documentation & Website Affects Versions: 1.0.0 Reporter: Andrew Lim Fix For: 1.0.0 The "view the data" and "modify the data" policies need to be included in the Admin Guide. Also, related screenshots need to be updated. Lastly, adding a table that shows Legacy roles and what policies they are given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2506) Update screenshot in README.md for new 1.0 UI
Andrew Lim created NIFI-2506: Summary: Update screenshot in README.md for new 1.0 UI Key: NIFI-2506 URL: https://issues.apache.org/jira/browse/NIFI-2506 Project: Apache NiFi Issue Type: Improvement Components: Documentation & Website Reporter: Andrew Lim Priority: Minor Fix For: 1.0.0 The screenshot in README.md should be updated for the new 1.0 UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2506) Update screenshot in README.md for new 1.0 UI
[ https://issues.apache.org/jira/browse/NIFI-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2506: - Attachment: nifi_first_launch_screenshot.png > Update screenshot in README.md for new 1.0 UI > - > > Key: NIFI-2506 > URL: https://issues.apache.org/jira/browse/NIFI-2506 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Andrew Lim >Priority: Minor > Fix For: 1.0.0 > > Attachments: nifi_first_launch_screenshot.png > > > The screenshot in README.md should be updated for the new 1.0 UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-2502) Update Multi-tenant Authorization section in Admin Guide for recent changes
[ https://issues.apache.org/jira/browse/NIFI-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-2502: Assignee: Andrew Lim > Update Multi-tenant Authorization section in Admin Guide for recent changes > --- > > Key: NIFI-2502 > URL: https://issues.apache.org/jira/browse/NIFI-2502 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > The "view the data" and "modify the data" policies need to be included in the > Admin Guide. Also, related screenshots need to be updated. > Lastly, adding a table that shows Legacy roles and what policies they are > given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2502) Update Multi-tenant Authorization section in Admin Guide for addition of data policies
[ https://issues.apache.org/jira/browse/NIFI-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2502: - Summary: Update Multi-tenant Authorization section in Admin Guide for addition of data policies (was: Update Multi-tenant Authorization section in Admin Guide for recent changes) > Update Multi-tenant Authorization section in Admin Guide for addition of data > policies > -- > > Key: NIFI-2502 > URL: https://issues.apache.org/jira/browse/NIFI-2502 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > The "view the data" and "modify the data" policies need to be included in the > Admin Guide. Also, related screenshots need to be updated. > Lastly, adding a table that shows Legacy roles and what policies they are > given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-2506) Update screenshot in README.md for new 1.0 UI
[ https://issues.apache.org/jira/browse/NIFI-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-2506: Assignee: Andrew Lim > Update screenshot in README.md for new 1.0 UI > - > > Key: NIFI-2506 > URL: https://issues.apache.org/jira/browse/NIFI-2506 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > Fix For: 1.0.0 > > Attachments: nifi_first_launch_screenshot.png > > > The screenshot in README.md should be updated for the new 1.0 UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2477) Document tls-toolkit
[ https://issues.apache.org/jira/browse/NIFI-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408354#comment-15408354 ] Andrew Lim commented on NIFI-2477: -- [~bryanrosan...@gmail.com], I've been working on docs for the 1.0.0 release and reviewed your rough draft. Here is a version with my edits: For the Admin guide (seems like it should go in the existing Security Configuration section): TLS Generation Toolkit In order to facilitate the secure setup of NiFi, a tls-toolkit command line utility is available to automatically generate the required keystores, truststore, and relevant configuration files. This is especially useful for securing multiple NiFi nodes, which can be a tedious and error-prone process. The tls-toolkit has two primary modes of operation: 1. Standalone -- generates the certificate authority, keystores, truststores, and nifi.properties files in one command. 2. Client/Server mode -- uses a Certificate Authority Server that accepts Certificate Signing Requests from clients, signs them, and sends the resulting certificates back. Both client and server validate the other’s identity through a shared secret. Standalone: Standalone mode can be invoked by running “tls-toolkit.sh standalone -h” which will print the usage information along with descriptions of options that can be specified. The most common options to specify are: 1. -n (or --hostnames) a comma-separated list of hostnames that you’d like to generate certificates for 2. -f (or --nifiPropertiesFile) a base nifi.properties file that the tool will update for each host 3. -o (or --outputDirectory) the directory to use for the resulting Certificate Authority files and NiFi configurations. A subdirectory will be made for each host. 4. -p (or --httpsPort) the https port in nifi.properties and enable secure site-to-site. This is optional and not required if you’ve provided a template nifi.properties. Client/Server: Client/Server mode relies on a long-running Certificate Authority (CA) to issue certificates. The CA can be stopped when you’re not bringing nodes online. Server: The CA server can be invoked by running “tls-toolkit server -h” which will print the usage information. The most common options to specify are: 1. -f (or --configJson) the location of the json config (written after first run) 2. -F (or --useConfigJson) load all relevant configuration from the config json (configJson is the only other argument necessary) 3. -t (or --token) the token used to prevent man in the middle attacks (this should be a long, random value and needs to be known when invoking the client) 4. -D (or --dn) the DN for the CA Client: The client can be used to request new Certificates from the CA. The client utility will generate a keypair andCertificate Signing Request (CSR) and send the CSR to the Certificate Authority. The client can be invoked by running “tls-toolkit.sh client -h” which will print the usage information. The most common options to specify are: 1. -f (or --configJson) the json config file 2. -c (or --certificateAuthorityHostname) the hostname of the CA 3. -D (or --DN) the DN for the CSR (and Certificate) 4. -t (or --token) the token used to prevent man in the middle attacks (this should be a long, random value and needs to be known when invoking the client) 5-T (or --keyStoreType) the type of keystore to create (specify jks for NiFi nodes, leave default to create client cert) After running the client you will have the CA’s certificate, a keystore, a truststore, and a config.json with information about them as well as their passwords. If you leave -T (or --keyStoreType) as its default value, PKCS12 will be used in order to make it easy to import into a browser for client certificates. For Developer Guide: NiFi Toolkit tls-toolkit - The Client/Server mode of operation came about from the desire to automatically generate required TLS configuration artifacts without needing to perform that generation in a centralized place. This simplifies configuration in a clustered environment. Since we don’t necessarily have a central place to run the generation logic or a trusted Certificate Authority, a shared secret is used to authenticate the clients and server to each other. The tls-toolkit prevents man in the middle attacks using HMAC verification of the public keys of the CA server and the CSR the client sends. A shared secret (the token) is used as the HMAC key. The basic process goes as follows: 1. The client generates a KeyPair. 2. The client generates a request json payload containing a CSR and an HMAC with the token as the key and the CSR’s public key fingerprint as the data. 3. The client connects to the CA Hostname at the https port specified and validates that the CN of the CA’s certificate matches the hostname (NOTE: because we don’t trust the CA at this point, this adds NO security, it is
[jira] [Updated] (NIFI-2451) Need to update Security Configuration content in Admin & Dev Guides for 1.0 changes
[ https://issues.apache.org/jira/browse/NIFI-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2451: - Summary: Need to update Security Configuration content in Admin & Dev Guides for 1.0 changes (was: Need to update Encryption Configuration in Admin Guide for 1.0 changes) > Need to update Security Configuration content in Admin & Dev Guides for 1.0 > changes > --- > > Key: NIFI-2451 > URL: https://issues.apache.org/jira/browse/NIFI-2451 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Will need to document changes being made in NIFI-1831 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2451) Need to update Encryption Configuration content in for 1.0 changes
[ https://issues.apache.org/jira/browse/NIFI-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2451: - Summary: Need to update Encryption Configuration content in for 1.0 changes (was: Need to update Security Configuration content in Admin & Dev Guides for 1.0 changes) > Need to update Encryption Configuration content in for 1.0 changes > -- > > Key: NIFI-2451 > URL: https://issues.apache.org/jira/browse/NIFI-2451 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Will need to document changes in Admin Guide for: > NIFI-1831 for Encryption Configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2451) Need to update Security Configuration content in Admin & Dev Guides for 1.0 changes
[ https://issues.apache.org/jira/browse/NIFI-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2451: - Description: Will need to document changes in Admin Guide for: NIFI-1831 for Encryption Configuration was: Will need to document changes in Admin Guide for: NIFI-1831 for Encryption Configuration NIFI-2193 for tls-toolkit utility Add toolkit section to Dev Guide for NIFI-2193 > Need to update Security Configuration content in Admin & Dev Guides for 1.0 > changes > --- > > Key: NIFI-2451 > URL: https://issues.apache.org/jira/browse/NIFI-2451 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Will need to document changes in Admin Guide for: > NIFI-1831 for Encryption Configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2451) Need to update Encryption Configuration content in for 1.0 changes
[ https://issues.apache.org/jira/browse/NIFI-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408345#comment-15408345 ] Andrew Lim commented on NIFI-2451: -- Modified ticket to include NIFI-2193 tls-toolkit doc, but there is a separate JIRA for that (NIFI-2477) > Need to update Encryption Configuration content in for 1.0 changes > -- > > Key: NIFI-2451 > URL: https://issues.apache.org/jira/browse/NIFI-2451 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Will need to document changes in Admin Guide for: > NIFI-1831 for Encryption Configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2297) Describe differences for QueryDatabaseTable between 0.x and 1.0
[ https://issues.apache.org/jira/browse/NIFI-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim resolved NIFI-2297. -- Resolution: Fixed Added as a bullet to 0.7.x to 1.0.0-BETA section of Migration Guide on NiFi Wiki: https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance > Describe differences for QueryDatabaseTable between 0.x and 1.0 > --- > > Key: NIFI-2297 > URL: https://issues.apache.org/jira/browse/NIFI-2297 > Project: Apache NiFi > Issue Type: Task > Components: Documentation & Website >Reporter: Matt Burgess >Assignee: Andrew Lim > Labels: migration > Fix For: 1.0.0 > > > QueryDatabaseTable was refactored to support a common interface > (DatabaseAdapter) between some DB-related processors that need to know the > "type" of database, either for SQL generation or whatever. Since > QueryDatabaseTable exists in 0.7.x, documentation is needed to describe the > changes that need to be made between "SQL Preprocessing Strategy" and > "Database Type". In the former property the choice is "None" or "Oracle"; in > the new system that property is invalid and the new one offers a choice of > "Generic" or "Oracle". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-1967) nifi.properties conversion for 1.0.0
[ https://issues.apache.org/jira/browse/NIFI-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim resolved NIFI-1967. -- Resolution: Fixed Updated Migration Guide on NiFi Wiki with system property changes in going from 0.7.x to 1.0.0. https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance > nifi.properties conversion for 1.0.0 > > > Key: NIFI-1967 > URL: https://issues.apache.org/jira/browse/NIFI-1967 > Project: Apache NiFi > Issue Type: Improvement > Components: Configuration, Documentation & Website >Affects Versions: 1.0.0 >Reporter: Matt Gilman >Assignee: Andrew Lim >Priority: Minor > Labels: migration > Fix For: 1.0.0 > > > With the properties changing it would be nice to offer an automated way of > converting an existing nifi.properties to the 1.0.0 version. Specifically, > the clustering properties have changed enough to warrant scripting this for > users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2173) LDAP provider referral strategy typo in Code
[ https://issues.apache.org/jira/browse/NIFI-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2173: - Labels: migration newbie (was: newbie) > LDAP provider referral strategy typo in Code > > > Key: NIFI-2173 > URL: https://issues.apache.org/jira/browse/NIFI-2173 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 0.6.0 >Reporter: Matthew Clarke >Assignee: Joseph Percivall >Priority: Minor > Labels: migration, newbie > Fix For: 1.0.0 > > > The LDAP referral strategy set in the login-identity-providers.xml file > should support IGNORE, FOLLOW, or THROW. If the referral strategy is set to > IGNORE, NiFi will fail to start and complain that the possible values are > [follow, ignore, throw]. The issue is that the code has a typo where IGNORE > is spelled INGORE. > WORKAROUND: Users can get around the issue by configuring the referral > strategy for INGORE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2434) Outdated information in Admin guide should be corrected for 1.0
Andrew Lim created NIFI-2434: Summary: Outdated information in Admin guide should be corrected for 1.0 Key: NIFI-2434 URL: https://issues.apache.org/jira/browse/NIFI-2434 Project: Apache NiFi Issue Type: Bug Components: Documentation & Website Affects Versions: 1.0.0 Reporter: Andrew Lim Assignee: Andrew Lim Fix For: 1.0.0 Besides new 1.0 features that should be added to the Admin guide, there is some info there that needs to be removed or updated. Some examples include: -removal of references to Java 7 and update to Java 8 -update supported browser versions -replace screenshots with new 1.0 UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2434) Outdated information in Admin guide should be corrected for 1.0
[ https://issues.apache.org/jira/browse/NIFI-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399762#comment-15399762 ] Andrew Lim commented on NIFI-2434: -- [~joewitt] thanks for catching that. I have changed my PR to include the processor screenshot that needed to be replaced as well (allow-weak-crypto.png). > Outdated information in Admin guide should be corrected for 1.0 > --- > > Key: NIFI-2434 > URL: https://issues.apache.org/jira/browse/NIFI-2434 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Fix For: 1.0.0 > > > Besides new 1.0 features that should be added to the Admin guide, there is > some info there that needs to be removed or updated. Some examples include: > -removal of references to Java 7 and update to Java 8 > -update supported browser versions > -replace screenshots with new 1.0 UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2420) Add a section for Multi-tenant Authorization to the Admin Guide
Andrew Lim created NIFI-2420: Summary: Add a section for Multi-tenant Authorization to the Admin Guide Key: NIFI-2420 URL: https://issues.apache.org/jira/browse/NIFI-2420 Project: Apache NiFi Issue Type: Bug Components: Documentation & Website Affects Versions: 1.0.0 Reporter: Andrew Lim Fix For: 1.0.0 Multi-tenant Authorization is a new feature in 1.0.0. A section covering setup and management should be included in the documentation. Attaching my first attempt at the doc in case anyone has any thoughts. I plan to submit a PR soon depending on feedback and after more editing/review on my part. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2286) Policies: "Add user to policy" and "Remove" icons do not have hover help text
[ https://issues.apache.org/jira/browse/NIFI-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414009#comment-15414009 ] Andrew Lim commented on NIFI-2286: -- The NiFi Users window also has the same "Add User " icon. That one needs hover text as well. Something like "Add User/Group" > Policies: "Add user to policy" and "Remove" icons do not have hover help text > -- > > Key: NIFI-2286 > URL: https://issues.apache.org/jira/browse/NIFI-2286 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Labels: UI > > The "Add user to policy" and "Remove" buttons in the Access Policies window > do not have any help text displayed when the user hovers over them. > This will be really helpful especially to new users of the Authorization API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2533) When searching for users to add to a policy, should filter out users that are already on the policy
Andrew Lim created NIFI-2533: Summary: When searching for users to add to a policy, should filter out users that are already on the policy Key: NIFI-2533 URL: https://issues.apache.org/jira/browse/NIFI-2533 Project: Apache NiFi Issue Type: Improvement Components: Core UI Affects Versions: 1.0.0 Reporter: Andrew Lim Priority: Minor As shown in the attached screenshot. User1 is already on the policy. When adding additional users to the policy, the "Search users" window should filter out User1 from the list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2532) Should add hover text to "Add User" and "Remove" icon
Andrew Lim created NIFI-2532: Summary: Should add hover text to "Add User" and "Remove" icon Key: NIFI-2532 URL: https://issues.apache.org/jira/browse/NIFI-2532 Project: Apache NiFi Issue Type: Improvement Components: Core UI Affects Versions: 1.0.0 Reporter: Andrew Lim Priority: Minor The "Add User" icon is used when adding users/groups and when adding users to policies. The "Remove" icon (trashcan) is used to remove policies. Both of these icons should have hover text so users will have a better idea of the action performed if clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2532) Should add hover text to "Add User" and "Remove" icons
[ https://issues.apache.org/jira/browse/NIFI-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2532: - Summary: Should add hover text to "Add User" and "Remove" icons (was: Should add hover text to "Add User" and "Remove" icon) > Should add hover text to "Add User" and "Remove" icons > -- > > Key: NIFI-2532 > URL: https://issues.apache.org/jira/browse/NIFI-2532 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > > The "Add User" icon is used when adding users/groups and when adding users to > policies. > The "Remove" icon (trashcan) is used to remove policies. > Both of these icons should have hover text so users will have a better idea > of the action performed if clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2533) When searching for users to add to a policy, should filter out users that are already on the policy
[ https://issues.apache.org/jira/browse/NIFI-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2533: - Attachment: NIFI-2533.png > When searching for users to add to a policy, should filter out users that are > already on the policy > --- > > Key: NIFI-2533 > URL: https://issues.apache.org/jira/browse/NIFI-2533 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Attachments: NIFI-2533.png > > > As shown in the attached screenshot. User1 is already on the policy. When > adding additional users to the policy, the "Search users" window should > filter out User1 from the list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2532) Should add hover text to "Add User" and "Remove" icons
[ https://issues.apache.org/jira/browse/NIFI-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim resolved NIFI-2532. -- Resolution: Duplicate Dupe of NIFI-2286 > Should add hover text to "Add User" and "Remove" icons > -- > > Key: NIFI-2532 > URL: https://issues.apache.org/jira/browse/NIFI-2532 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > > The "Add User" icon is used when adding users/groups and when adding users to > policies. > The "Remove" icon (trashcan) is used to remove policies. > Both of these icons should have hover text so users will have a better idea > of the action performed if clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2286) Policies: "Add user to policy" and "Remove" icons do not have hover help text
[ https://issues.apache.org/jira/browse/NIFI-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2286: - Issue Type: Improvement (was: Bug) > Policies: "Add user to policy" and "Remove" icons do not have hover help text > -- > > Key: NIFI-2286 > URL: https://issues.apache.org/jira/browse/NIFI-2286 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Labels: UI > > The "Add user to policy" and "Remove" buttons in the Access Policies window > do not have any help text displayed when the user hovers over them. > This will be really helpful especially to new users of the Authorization API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2286) Policies: "Add user to policy" and "Remove" icons do not have hover help text
[ https://issues.apache.org/jira/browse/NIFI-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2286: - Affects Version/s: (was: 1.1.0) 1.0.0 > Policies: "Add user to policy" and "Remove" icons do not have hover help text > -- > > Key: NIFI-2286 > URL: https://issues.apache.org/jira/browse/NIFI-2286 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Labels: UI > > The "Add user to policy" and "Remove" buttons in the Access Policies window > do not have any help text displayed when the user hovers over them. > This will be really helpful especially to new users of the Authorization API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] (NIFI-352) Consider Sticky Bulletins
[ https://issues.apache.org/jira/browse/NIFI-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847174#comment-15847174 ] Andrew Lim commented on NIFI-352: - A notification window/system in NiFi is something that I think is sorely needed, especially as more and more features are added. There should be a central place where the user can view and interact with issues that are affecting the flow or the user's ability to modify the flow. I agree with [~rmoran] that it would make sense conceptually to the user to expand the Bulletin implementation for this. Perhaps a new Jira is needed, since this is much larger/different than the concept of "sticky" bulletins. > Consider Sticky Bulletins > - > > Key: NIFI-352 > URL: https://issues.apache.org/jira/browse/NIFI-352 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Daniel Ueberfluss >Priority: Minor > Labels: dashboard > > Consider the implementation of Sticky Bulletins for things like "Controller > Failed to Start Processor XYZ" > A user should have the ability to Confirm the bulletin; until that time it > should stay present. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (NIFI-3392) Enhance documentation for provenance event type definitions
[
https://issues.apache.org/jira/browse/NIFI-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Lim reassigned NIFI-3392:
Assignee: Andrew Lim
> Enhance documentation for provenance event type definitions
> ---
>
> Key: NIFI-3392
> URL: https://issues.apache.org/jira/browse/NIFI-3392
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
>Affects Versions: 1.1.1
>Reporter: Andy LoPresto
>Assignee: Andrew Lim
>
> The provenance events can be unfamiliar to new users, and the nuance of the
> event types can be confusing even to experienced users and developers. The
> documentation should be improved to contain a definition table of the various
> event types ({{CREATE}}, {{DROP}}, etc.), their meaning, and (for developers)
> when to use each type if writing their own provenance reporting code.
> A comprehensive list of event types is available (and discussed somewhat) in
> [{{ProvenanceEventType.java}}|https://github.com/apache/nifi/blob/master/nifi-api/src/main/java/org/apache/nifi/provenance/ProvenanceEventType.java].
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-1796) Create the 'Hello World' example of custom processor development
[ https://issues.apache.org/jira/browse/NIFI-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832339#comment-15832339 ] Andrew Lim commented on NIFI-1796: -- This doesn't help solve the core issue of this ticket, but related to the documentation comments, I filed https://issues.apache.org/jira/browse/NIFI-3345. Basically, since the processor list is so long now, we could make the left nav sections of the doc collapsible so areas like the Developer Guide are no longer obscured. > Create the 'Hello World' example of custom processor development > > > Key: NIFI-1796 > URL: https://issues.apache.org/jira/browse/NIFI-1796 > Project: Apache NiFi > Issue Type: Task > Components: Documentation & Website >Reporter: Joseph Witt >Assignee: Oleg Zhurakousky > > We really need to create a simple guide for how to build custom processor in > nifi. The sort of 'hello world' example. > This was created due to finding it hard to give a nice simple short pointer > for a question on the mailing list. > We do have a solid developer guide here [1] that goes into the key concepts > and processor development a bit. The next best thing is to use the supplied > maven archetype to lay down the fundamental pieces. You can read a bit more > about that here [2]. Finally something that is also quite helpful is looking > at the standard processors to see if anything follows the pattern/problem you > had in mind and which can serve as a good basis [3] > [1] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html > [2] > https://richardstechnotes.wordpress.com/2015/12/06/setting-up-for-custom-nifi-processor-development/ > [3] > https://github.com/apache/nifi/tree/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-3526) Update secure site-to-site section of User Guide that references Access Control
[ https://issues.apache.org/jira/browse/NIFI-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-3526: Assignee: Andrew Lim > Update secure site-to-site section of User Guide that references Access > Control > --- > > Key: NIFI-3526 > URL: https://issues.apache.org/jira/browse/NIFI-3526 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > > The Access Control paragraph in the "Configure Site-to-Site server NiFi > instance" section of the User Guide [1] needs to be updated for 1.x > functionality. > [1] > https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#configure-site-to-site-server-nifi-instance -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3526) Update secure site-to-site section of User Guide
Andrew Lim created NIFI-3526: Summary: Update secure site-to-site section of User Guide Key: NIFI-3526 URL: https://issues.apache.org/jira/browse/NIFI-3526 Project: Apache NiFi Issue Type: Bug Components: Documentation & Website Affects Versions: 1.0.0 Reporter: Andrew Lim The Access Control paragraph in the "Configure Site-to-Site server NiFi instance" section of the User Guide [1] needs to be updated for 1.x functionality. [1] https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#configure-site-to-site-server-nifi-instance -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3526) Update secure site-to-site section of User Guide that references Access Control
[ https://issues.apache.org/jira/browse/NIFI-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-3526: - Summary: Update secure site-to-site section of User Guide that references Access Control (was: Update secure site-to-site section of User Guide) > Update secure site-to-site section of User Guide that references Access > Control > --- > > Key: NIFI-3526 > URL: https://issues.apache.org/jira/browse/NIFI-3526 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.0.0 >Reporter: Andrew Lim > > The Access Control paragraph in the "Configure Site-to-Site server NiFi > instance" section of the User Guide [1] needs to be updated for 1.x > functionality. > [1] > https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#configure-site-to-site-server-nifi-instance -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (NIFI-3480) Fix incorrect Admin Guide documentation regarding anonymous access
[
https://issues.apache.org/jira/browse/NIFI-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Lim reassigned NIFI-3480:
Assignee: Andrew Lim
> Fix incorrect Admin Guide documentation regarding anonymous access
> --
>
> Key: NIFI-3480
> URL: https://issues.apache.org/jira/browse/NIFI-3480
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
>Affects Versions: 1.1.1
>Reporter: Andy LoPresto
>Assignee: Andrew Lim
>Priority: Trivial
> Labels: documentation, security
>
> The Admin Guide *Security Configuration* section states
> {quote}
> {{nifi.security.truststore}}
> Filename of the Truststore that will be used to authorize those connecting to
> NiFi. If not set, all who attempt to connect will be provided access as the
> *Anonymous* user.
> {quote}
> This is incorrect and misleading. The only way to configure a secured
> instance with anonymous access is via LDAP or Kerberos and configuration of
> the authorizer to explicitly allow anonymous access. Configuring a secured
> instance with no truststore will simply refuse all incoming connections.
> With {{nifi.security.needClientAuth}} set to {{true}} or empty (default):
> {code}
> 2017-02-14 12:03:05,546 WARN [Thread-1]
> org.apache.nifi.web.server.JettyServer Failed to stop web server
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'flowService': FactoryBean threw exception on object creation;
> nested exception is org.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'flowController': FactoryBean threw exception
> on object creation; nested exception is
> org.apache.nifi.framework.security.util.SslContextCreationException: Need
> client auth is set to 'true', but no truststore properties are configured.
> at
> org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:175)
> ~[na:na]
> at
> org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:103)
> ~[na:na]
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1585)
> ~[na:na]
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:254)
> ~[na:na]
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
> ~[na:na]
> at
> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1060)
> ~[na:na]
> at
> org.apache.nifi.web.contextlistener.ApplicationStartupContextListener.contextDestroyed(ApplicationStartupContextListener.java:103)
> ~[na:na]
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:845)
> ~[na:na]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:546)
> ~[na:na]
> at
> org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:826)
> ~[na:na]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:356)
> ~[na:na]
> at
> org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1410)
> ~[na:na]
> at
> org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1374)
> ~[na:na]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:874)
> ~[na:na]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:272)
> ~[na:na]
> at
> org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:544) ~[na:na]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
> ~[na:na]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143)
> ~[na:na]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161)
> ~[na:na]
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73)
> ~[na:na]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
> ~[na:na]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143)
> ~[na:na]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161)
> ~[na:na]
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73)
> ~[na:na]
> at
>
[jira] [Resolved] (NIFI-3438) Ability to link to a view in Nifi (process group, processor, etc...)
[ https://issues.apache.org/jira/browse/NIFI-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim resolved NIFI-3438. -- Resolution: Duplicate Thanks [~ncarenza]. Closing as dupe. > Ability to link to a view in Nifi (process group, processor, etc...) > > > Key: NIFI-3438 > URL: https://issues.apache.org/jira/browse/NIFI-3438 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Nicholas Carenza >Priority: Minor > > I would like to be able to share a link to a particular view in the Nifi UI. > For example: > #/ might just bring me to that processor, center it in view and > reset the zoom. If it is a process group, it might go to it an bring all > processors into view. > #//config might then also bring up the configuration for that > processor > #//config/properties might then also set the tab to 'properties' -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3493) Security configuration section in Admin Guide incorrectly refers to nifi.web.http.network.interface instead of nifi.web.https.network.interface
Andrew Lim created NIFI-3493: Summary: Security configuration section in Admin Guide incorrectly refers to nifi.web.http.network.interface instead of nifi.web.https.network.interface Key: NIFI-3493 URL: https://issues.apache.org/jira/browse/NIFI-3493 Project: Apache NiFi Issue Type: Bug Components: Documentation & Website Affects Versions: 1.2.0 Reporter: Andrew Lim Priority: Minor Here is the reference in the Admin Guide: To allow admins to configure the application to run only on specific network interfaces, nifi.web.http.network.interface* or nifi.web.http.network.interface* properties can be specified. The second property should refer to HTTPS: nifi.web.https.network.interface* -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (NIFI-3493) Security configuration section in Admin Guide incorrectly refers to nifi.web.http.network.interface instead of nifi.web.https.network.interface
[ https://issues.apache.org/jira/browse/NIFI-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-3493: Assignee: Andrew Lim > Security configuration section in Admin Guide incorrectly refers to > nifi.web.http.network.interface instead of nifi.web.https.network.interface > --- > > Key: NIFI-3493 > URL: https://issues.apache.org/jira/browse/NIFI-3493 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.2.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > Here is the reference in the Admin Guide: > To allow admins to configure the application to run only on specific network > interfaces, nifi.web.http.network.interface* or > nifi.web.http.network.interface* properties can be specified. > The second property should refer to HTTPS: nifi.web.https.network.interface* -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3493) Security configuration section in Admin Guide incorrectly refers to nifi.web.http.network.interface instead of nifi.web.https.network.interface
[ https://issues.apache.org/jira/browse/NIFI-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-3493: - Description: Here is the reference in the Admin Guide: "To allow admins to configure the application to run only on specific network interfaces, nifi.web.http.network.interface* or nifi.web.http.network.interface* properties can be specified." The second property should refer to HTTPS: nifi.web.https.network.interface* was: Here is the reference in the Admin Guide: To allow admins to configure the application to run only on specific network interfaces, nifi.web.http.network.interface* or nifi.web.http.network.interface* properties can be specified. The second property should refer to HTTPS: nifi.web.https.network.interface* > Security configuration section in Admin Guide incorrectly refers to > nifi.web.http.network.interface instead of nifi.web.https.network.interface > --- > > Key: NIFI-3493 > URL: https://issues.apache.org/jira/browse/NIFI-3493 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.2.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > Here is the reference in the Admin Guide: > "To allow admins to configure the application to run only on specific network > interfaces, nifi.web.http.network.interface* or > nifi.web.http.network.interface* properties can be specified." > The second property should refer to HTTPS: nifi.web.https.network.interface* -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3340) Modify description of the Directory property for PutHDFS to say it will create the directory if it doesn't exist
[ https://issues.apache.org/jira/browse/NIFI-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-3340: - Description: The current description for the "Directory" property for PutHDFS only states: The parent HDFS directory to which files should be written It would be helpful to add: The directory will be created if it doesn't exist. was: The current description for the "Directory" property for PutHDFS only states: The parent HDFS directory to which files should be written It would be helpful to add: Missing destination directories will be created. > Modify description of the Directory property for PutHDFS to say it will > create the directory if it doesn't exist > > > Key: NIFI-3340 > URL: https://issues.apache.org/jira/browse/NIFI-3340 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Trivial > > The current description for the "Directory" property for PutHDFS only states: > The parent HDFS directory to which files should be written > It would be helpful to add: > The directory will be created if it doesn't exist. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3340) Modify description of the Directory property for PutHDFS to say it will create the directory if it doesn't exist
[ https://issues.apache.org/jira/browse/NIFI-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-3340: - Description: The current description for the "Directory" property for PutHDFS only states: The parent HDFS directory to which files should be written It would be helpful to add: Missing destination directories will be created. was: The current description for the "Directory" property for PutHDFS only states: The parent HDFS directory to which files should be written Supports Expression Language: true It would be helpful to add: Missing destination directories will be created. > Modify description of the Directory property for PutHDFS to say it will > create the directory if it doesn't exist > > > Key: NIFI-3340 > URL: https://issues.apache.org/jira/browse/NIFI-3340 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Trivial > > The current description for the "Directory" property for PutHDFS only states: > The parent HDFS directory to which files should be written > It would be helpful to add: > Missing destination directories will be created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-3035) URL to display a particular process group in UI
[ https://issues.apache.org/jira/browse/NIFI-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888662#comment-15888662 ] Andrew Lim commented on NIFI-3035: -- Thanks [~scottyaslan]. I filed NIFI-3539 and put it under the Epic you suggested. NIFI-3539 captures adding "deep linking" functionality as a whole. We can break it up as needed when there is bandwidth to work on this new feature. > URL to display a particular process group in UI > --- > > Key: NIFI-3035 > URL: https://issues.apache.org/jira/browse/NIFI-3035 > Project: Apache NiFi > Issue Type: New Feature > Components: Core UI >Reporter: Christine Draper >Assignee: Scott Aslan > > Our use case has multiple teams of users working on specific process groups. > We would like to be able to give them a URL that will launch the UI on the > specific group they are working on, rather than them having to navigate to it > from the root group. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3539) Add "deep linking" capability to NiFi
Andrew Lim created NIFI-3539: Summary: Add "deep linking" capability to NiFi Key: NIFI-3539 URL: https://issues.apache.org/jira/browse/NIFI-3539 Project: Apache NiFi Issue Type: New Feature Components: Core UI Reporter: Andrew Lim Provide exact URLs to specific areas/views of the application. Examples: -In the Data provenance window, a URL could show results for a specific search with sorting applied -A URL which highlights a processor, centers it in view and resets the zoom. -Similarly, a URL which opens the configuration window for a specific processor and takes the user to a specific configuration tab -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (NIFI-2639) Update graphics in "Apache NiFi In Depth" doc
[ https://issues.apache.org/jira/browse/NIFI-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-2639: Assignee: Andrew Lim > Update graphics in "Apache NiFi In Depth" doc > - > > Key: NIFI-2639 > URL: https://issues.apache.org/jira/browse/NIFI-2639 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Joseph Percivall >Assignee: Andrew Lim >Priority: Minor > Fix For: 1.1.0 > > > There are a number of graphics in the "Apache NiFi In Depth" that are screen > shots of a flow that currently are of the 0.x UI. > For aesthetics purposes, these should be updated using the new UI . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2277) Policies: Get an "An unexpected type of resource in this policy /flow" error trying to access global policies
[ https://issues.apache.org/jira/browse/NIFI-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2277: - Assignee: Andrew Lim (was: Scott Aslan) > Policies: Get an "An unexpected type of resource in this policy /flow" error > trying to access global policies > -- > > Key: NIFI-2277 > URL: https://issues.apache.org/jira/browse/NIFI-2277 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Labels: UI > Attachments: NIFI-2277_globalError.png > > > Launched secured NiFi instance. If I immediately select "Policies" from the > control menu, the Access Policies window is displayed as expected. > If I select a processor on the canvas that I do not have view policies on, I > get an error (https://issues.apache.org/jira/browse/NIFI-2273). Now if I > select "Policies" from the control menu, I get an error: > An unexpected type of resource in this policy /flow > See attached screenshot. > Here is the link to this error in my NiFi instance: > https://localhost:8443/nifi-api/policies/read/flow/6bbc2432-9896-4bf2-ba2d-fa379d91684e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2277) Policies: Get an "An unexpected type of resource in this policy /flow" error trying to access global policies
[ https://issues.apache.org/jira/browse/NIFI-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15523716#comment-15523716 ] Andrew Lim commented on NIFI-2277: -- [~scottyaslan] Will check it out. Thanks! > Policies: Get an "An unexpected type of resource in this policy /flow" error > trying to access global policies > -- > > Key: NIFI-2277 > URL: https://issues.apache.org/jira/browse/NIFI-2277 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Andrew Lim > Labels: UI > Attachments: NIFI-2277_globalError.png > > > Launched secured NiFi instance. If I immediately select "Policies" from the > control menu, the Access Policies window is displayed as expected. > If I select a processor on the canvas that I do not have view policies on, I > get an error (https://issues.apache.org/jira/browse/NIFI-2273). Now if I > select "Policies" from the control menu, I get an error: > An unexpected type of resource in this policy /flow > See attached screenshot. > Here is the link to this error in my NiFi instance: > https://localhost:8443/nifi-api/policies/read/flow/6bbc2432-9896-4bf2-ba2d-fa379d91684e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2844) The icon for the component is cut-off in the Cluster Summary window.
[ https://issues.apache.org/jira/browse/NIFI-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15533595#comment-15533595 ] Andrew Lim commented on NIFI-2844: -- Note: For processors, the icon itself is incorrect. The Data Provenance icon is used instead of the Processor icon. I can create a separate Jira for this if necessary. > The icon for the component is cut-off in the Cluster Summary > window. > > > Key: NIFI-2844 > URL: https://issues.apache.org/jira/browse/NIFI-2844 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > > In a clustered environment, select "Summary" from the Global Menu. > As an example, in the Processors tab, select "View processor details" icon > (the 3 cube cluster icon) for one of the processors. The icon shown for the > processor is cut-off at the top. > This also occurs for the following components: > -Input Ports > -Output Ports > -Connections > Screenshots attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2844) The icon for the component is cut-off in the Cluster Summary window.
Andrew Lim created NIFI-2844: Summary: The icon for the component is cut-off in the Cluster Summary window. Key: NIFI-2844 URL: https://issues.apache.org/jira/browse/NIFI-2844 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.0.0 Reporter: Andrew Lim Priority: Minor In a clustered environment, select "Summary" from the Global Menu. As an example, in the Processors tab, select "View processor details" icon (the 3 cube cluster icon) for one of the processors. The icon shown for the processor is cut-off at the top. This also occurs for the following components: -Input Ports -Output Ports -Connections Screenshots attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2844) The icon for the component is cut-off in the Cluster Summary window.
[ https://issues.apache.org/jira/browse/NIFI-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15533615#comment-15533615 ] Andrew Lim commented on NIFI-2844: -- Also, consider making the icons and text larger if possible to improve readability. > The icon for the component is cut-off in the Cluster Summary > window. > > > Key: NIFI-2844 > URL: https://issues.apache.org/jira/browse/NIFI-2844 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Attachments: NIFI-2844_connection.png, NIFI-2844_inputPort.png, > NIFI-2844_outputPort.png, NIFI-2844_processor.png > > > In a clustered environment, select "Summary" from the Global Menu. > As an example, in the Processors tab, select "View processor details" icon > (the 3 cube cluster icon) for one of the processors. The icon shown for the > processor is cut-off at the top. > This also occurs for the following components: > -Input Ports > -Output Ports > -Connections > Screenshots attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2838) In the Advanced UI, if the Rule name is very long, the "x" to delete the rule becomes unavailable
[ https://issues.apache.org/jira/browse/NIFI-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2838: - Priority: Minor (was: Major) > In the Advanced UI, if the Rule name is very long, the "x" to delete the rule > becomes unavailable > - > > Key: NIFI-2838 > URL: https://issues.apache.org/jira/browse/NIFI-2838 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Labels: UI > Attachments: NIFI-2838_noDeleteIcon.png > > > As shown in the attached screenshot, when the rule name is very long it > extends the whole width of the bar, so the "x" to delete the rule is no > longer selectable. > Note: There is also a scroll bar that appears in this part of the UI, which I > thought would possibly reveal the "x", but the scroll bar doesn't appear to > add any value. The width of the rule name bar doesn't extend the width of > the space. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2840) Not clear how templates are ordered when adding to canvas
[ https://issues.apache.org/jira/browse/NIFI-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2840: - Attachment: NIFI-2840_NiFiClusterFilter.png > Not clear how templates are ordered when adding to canvas > - > > Key: NIFI-2840 > URL: https://issues.apache.org/jira/browse/NIFI-2840 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Labels: UI > Attachments: NIFI-2840_NiFiClusterFilter.png, > NIFI-2840_addTemplateOrder.png > > > As shown in the attached screenshot, the ordering of the templates is not > alphabetical. It is also not ordered by time of import. > If there is an ordering being applied, it should be made more > transparent/obvious to the user. > My personal preference is for the ordering to be done by last imported. So > the top-most available selection is the most recently imported template, > which would seem logical. I'm assuming if a user has imported a template, > he/she would like to then immediately add it to the flow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2847) In NiFi Cluster window, filtering "by status" or "by address" do not work as expected
[ https://issues.apache.org/jira/browse/NIFI-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2847: - Attachment: NIFI-2847_NiFiClusterFilter.png > In NiFi Cluster window, filtering "by status" or "by address" do not work as > expected > - > > Key: NIFI-2847 > URL: https://issues.apache.org/jira/browse/NIFI-2847 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Attachments: NIFI-2847_NiFiClusterFilter.png > > > Attaching a screenshot of what this window displays when no filters are > applied to the displayed results. > When filtering "by status": > -If I enter "CONNECTED", all 3 results are shown. > -But if I enter "CONNECTED," or "COORDINATOR", no results are shown. I > expected this to filter out all nodes except the cluster coordinator. > When filtering "by address": > -if I enter "localhost", all 3 results are shown. > -But if I enter "localhost:" or any of the ports (9443, for example), no > results are shown. I think it is a very common use case to filter by port. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2847) In NiFi Cluster window, filtering "by status" or "by address" do not work as expected
[ https://issues.apache.org/jira/browse/NIFI-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2847: - Description: Attaching a screenshot of what this window displays when no filters are applied to the displayed results for a 3 node cluster. When filtering "by status": -If I enter "CONNECTED", all 3 results are shown. -But if I enter "CONNECTED," or "COORDINATOR", no results are shown. I expected this to filter out all nodes except the cluster coordinator. When filtering "by address": -if I enter "localhost", all 3 results are shown. -But if I enter "localhost:" or any of the ports (9443, for example), no results are shown. I think it is a very common use case to filter by port. was: Attaching a screenshot of what this window displays when no filters are applied to the displayed results. When filtering "by status": -If I enter "CONNECTED", all 3 results are shown. -But if I enter "CONNECTED," or "COORDINATOR", no results are shown. I expected this to filter out all nodes except the cluster coordinator. When filtering "by address": -if I enter "localhost", all 3 results are shown. -But if I enter "localhost:" or any of the ports (9443, for example), no results are shown. I think it is a very common use case to filter by port. > In NiFi Cluster window, filtering "by status" or "by address" do not work as > expected > - > > Key: NIFI-2847 > URL: https://issues.apache.org/jira/browse/NIFI-2847 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Attachments: NIFI-2847_NiFiClusterFilter.png > > > Attaching a screenshot of what this window displays when no filters are > applied to the displayed results for a 3 node cluster. > When filtering "by status": > -If I enter "CONNECTED", all 3 results are shown. > -But if I enter "CONNECTED," or "COORDINATOR", no results are shown. I > expected this to filter out all nodes except the cluster coordinator. > When filtering "by address": > -if I enter "localhost", all 3 results are shown. > -But if I enter "localhost:" or any of the ports (9443, for example), no > results are shown. I think it is a very common use case to filter by port. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2846) Align text in Global Menu
[ https://issues.apache.org/jira/browse/NIFI-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2846: - Attachment: NIFI-2846_globalMenuText.png > Align text in Global Menu > - > > Key: NIFI-2846 > URL: https://issues.apache.org/jira/browse/NIFI-2846 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Attachments: NIFI-2846_globalMenuText.png > > > As shown in the attached screenshot, the text of the selections available in > the Global Menu are not aligned. "Cluster" is the most obvious. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2840) Not clear how templates are ordered when adding to canvas
[ https://issues.apache.org/jira/browse/NIFI-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2840: - Attachment: NIFI-2840_addTemplateOrder.png > Not clear how templates are ordered when adding to canvas > - > > Key: NIFI-2840 > URL: https://issues.apache.org/jira/browse/NIFI-2840 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Labels: UI > Attachments: NIFI-2840_addTemplateOrder.png > > > As shown in the attached screenshot, the ordering of the templates is not > alphabetical. It is also not ordered by time of import. > If there is an ordering being applied, it should be made more > transparent/obvious to the user. > My personal preference is for the ordering to be done by last imported. So > the top-most available selection is the most recently imported template, > which would seem logical. I'm assuming if a user has imported a template, > he/she would like to then immediately add it to the flow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2838) In the Advanced UI, if the Rule name is very long, the "x" to delete the rule becomes unavailable
[ https://issues.apache.org/jira/browse/NIFI-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15533945#comment-15533945 ] Andrew Lim commented on NIFI-2838: -- I just noticed that the "x" to delete the rule can become visible if you resize the browser window enough to reveal the entire rule name. However, this is still a problem though for a really long rule name, where even resizing doesn't help. > In the Advanced UI, if the Rule name is very long, the "x" to delete the rule > becomes unavailable > - > > Key: NIFI-2838 > URL: https://issues.apache.org/jira/browse/NIFI-2838 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Labels: UI > Attachments: NIFI-2838_noDeleteIcon.png > > > As shown in the attached screenshot, when the rule name is very long it > extends the whole width of the bar, so the "x" to delete the rule is no > longer selectable. > Note: There is also a scroll bar that appears in this part of the UI, which I > thought would possibly reveal the "x", but the scroll bar doesn't appear to > add any value. The width of the rule name bar doesn't extend the width of > the space. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2838) In the Advanced UI, if the Rule name is very long, the "x" to delete the rule becomes unavailable
[ https://issues.apache.org/jira/browse/NIFI-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2838: - Attachment: NIFI-2838_noDeleteIcon.png > In the Advanced UI, if the Rule name is very long, the "x" to delete the rule > becomes unavailable > - > > Key: NIFI-2838 > URL: https://issues.apache.org/jira/browse/NIFI-2838 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Labels: UI > Attachments: NIFI-2838_noDeleteIcon.png > > > As shown in the attached screenshot, when the rule name is very long it > extends the whole width of the bar, so the "x" to delete the rule is no > longer selectable. > Note: There is also a scroll bar that appears in this part of the UI, which I > thought would possibly reveal the "x", but the scroll bar doesn't appear to > add any value. The width of the rule name bar doesn't extend the width of > the space. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2844) The icon for the component is cut-off in the Cluster Summary window.
[ https://issues.apache.org/jira/browse/NIFI-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-2844: - Attachment: NIFI-2844_processor.png NIFI-2844_outputPort.png NIFI-2844_inputPort.png NIFI-2844_connection.png > The icon for the component is cut-off in the Cluster Summary > window. > > > Key: NIFI-2844 > URL: https://issues.apache.org/jira/browse/NIFI-2844 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Minor > Attachments: NIFI-2844_connection.png, NIFI-2844_inputPort.png, > NIFI-2844_outputPort.png, NIFI-2844_processor.png > > > In a clustered environment, select "Summary" from the Global Menu. > As an example, in the Processors tab, select "View processor details" icon > (the 3 cube cluster icon) for one of the processors. The icon shown for the > processor is cut-off at the top. > This also occurs for the following components: > -Input Ports > -Output Ports > -Connections > Screenshots attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2846) Align text in Global Menu
Andrew Lim created NIFI-2846: Summary: Align text in Global Menu Key: NIFI-2846 URL: https://issues.apache.org/jira/browse/NIFI-2846 Project: Apache NiFi Issue Type: Improvement Components: Core UI Affects Versions: 1.0.0 Reporter: Andrew Lim Priority: Minor As shown in the attached screenshot, the text of the selections available in the Global Menu are not aligned. "Cluster" is the most obvious. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
