[jira] [Created] (KNOX-1779) Add HTTP X-XSS-Protection response header support for WebAppSec Provider
Krishna Pandey created KNOX-1779: Summary: Add HTTP X-XSS-Protection response header support for WebAppSec Provider Key: KNOX-1779 URL: https://issues.apache.org/jira/browse/KNOX-1779 Project: Apache Knox Issue Type: Improvement Components: Server Affects Versions: 1.2.0 Reporter: Krishna Pandey Assignee: Krishna Pandey Fix For: 1.3.0 Support to add X-XSS-Protection HTTP response header in Knox's WebAppSec Provider enabling modern web browsers to detect and thwart Cross-site Scripting (XSS) attacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (KNOX-1162) Improve diagnostics for conf/krb5JAASLogin.conf misconfiguration
[
https://issues.apache.org/jira/browse/KNOX-1162?focusedWorklogId=200227=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-200227
]
ASF GitHub Bot logged work on KNOX-1162:
Author: ASF GitHub Bot
Created on: 18/Feb/19 19:30
Start Date: 18/Feb/19 19:30
Worklog Time Spent: 10m
Work Description: smolnar82 commented on pull request #55: KNOX-1162 -
Logging stacktrace for FATAL messages and displaying a meaningful error message
in case of missing/non-parsable JAAS configuration
URL: https://github.com/apache/knox/pull/55#discussion_r257807719
##
File path:
gateway-service-remoteconfig/src/main/java/org/apache/knox/gateway/service/config/remote/zk/RemoteConfigurationRegistryJAASConfig.java
##
@@ -49,17 +51,26 @@
private static final RemoteConfigurationMessages log =
MessagesFactory.get(RemoteConfigurationMessages.class);
// Cache the current JAAS configuration
-private Configuration delegate = Configuration.getConfiguration();
+private final Configuration delegate;
-private AliasService aliasService;
+private final AliasService aliasService;
-private Map contextEntries = new
HashMap<>();
+private final Map contextEntries = new
HashMap<>();
static RemoteConfigurationRegistryJAASConfig
configure(List configs, AliasService
aliasService) {
return new RemoteConfigurationRegistryJAASConfig(configs,
aliasService);
}
private
RemoteConfigurationRegistryJAASConfig(List
configs, AliasService aliasService) {
+try {
+ delegate = Configuration.getConfiguration();
+} catch(Exception e) {
+ //populate the original error with a meaningful message; logging
will happen later in the upper in the call hierarchy
Review comment:
Fixed; thanks for the review!
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 200227)
Time Spent: 50m (was: 40m)
> Improve diagnostics for conf/krb5JAASLogin.conf misconfiguration
>
>
> Key: KNOX-1162
> URL: https://issues.apache.org/jira/browse/KNOX-1162
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
>Affects Versions: 0.14.0
>Reporter: Kevin Minder
>Assignee: Sandor Molnar
>Priority: Minor
> Fix For: 1.3.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When there is a misconfiguration in conf/krb5JAASLogin.conf the server fails
> to start and the information in gateway.log isn't at all helpful. So two
> requests
> # Logging should indicate at a minimum what file contains the issue.
> # All fatal issues should log stack traces without requiring enabling debug
> logging.
> This is the error shown in gateway.log
> {code}
> 2018-01-05 12:05:12,538 FATAL hadoop.gateway (GatewayServer.java:main(163)) -
> Failed to start gateway: java.lang.SecurityException: java.io.IOException:
> Configuration Error:
> Line 7: expected [option key]
> {code}
> When you enabled debug logging you get somewhat better information.
> {code}
> 2018-01-05 15:55:54,087 FATAL hadoop.gateway (GatewayServer.java:main(163)) -
> Failed to start gateway: java.lang.SecurityException: java.io.IOException:
> Configuration Error:
> Line 7: expected [option key]
> java.lang.SecurityException: java.io.IOException: Configuration Error:
> Line 7: expected [option key]
> at sun.security.provider.ConfigFile$Spi.(ConfigFile.java:137)
> at sun.security.provider.ConfigFile.(ConfigFile.java:102)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at
> javax.security.auth.login.Configuration$2.run(Configuration.java:255)
> at
> javax.security.auth.login.Configuration$2.run(Configuration.java:247)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> javax.security.auth.login.Configuration.getConfiguration(Configuration.java:246)
> at
>
[GitHub] smolnar82 commented on a change in pull request #55: KNOX-1162 - Logging stacktrace for FATAL messages and displaying a meaningful error message in case of missing/non-parsable JAAS configura
smolnar82 commented on a change in pull request #55: KNOX-1162 - Logging
stacktrace for FATAL messages and displaying a meaningful error message in case
of missing/non-parsable JAAS configuration
URL: https://github.com/apache/knox/pull/55#discussion_r257807719
##
File path:
gateway-service-remoteconfig/src/main/java/org/apache/knox/gateway/service/config/remote/zk/RemoteConfigurationRegistryJAASConfig.java
##
@@ -49,17 +51,26 @@
private static final RemoteConfigurationMessages log =
MessagesFactory.get(RemoteConfigurationMessages.class);
// Cache the current JAAS configuration
-private Configuration delegate = Configuration.getConfiguration();
+private final Configuration delegate;
-private AliasService aliasService;
+private final AliasService aliasService;
-private Map contextEntries = new
HashMap<>();
+private final Map contextEntries = new
HashMap<>();
static RemoteConfigurationRegistryJAASConfig
configure(List configs, AliasService
aliasService) {
return new RemoteConfigurationRegistryJAASConfig(configs,
aliasService);
}
private
RemoteConfigurationRegistryJAASConfig(List
configs, AliasService aliasService) {
+try {
+ delegate = Configuration.getConfiguration();
+} catch(Exception e) {
+ //populate the original error with a meaningful message; logging
will happen later in the upper in the call hierarchy
Review comment:
Fixed; thanks for the review!
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
Re: [DISCUSS] Planning for Apache Knox 1.3.0 Release
Larry... Being new to the project, I do not have much to contribute related to the changes for 1.3.0; however, this seems like a pretty large list of items. Mid-April seems optimistic to me, but then again I am new to the team and not sure how quickly we work. That said, I am up for the challenge. One thing to note on the SSO items is that Knox may need some cleanup on how the signing key is configured. The current set of configuration properties used to declare where to find it is lacking and assumes that the decryption keys for the keystore and key are the master key (with a little hack in there to customize password for the key). I think this should be more consistent with how the custom identity and trust store locations facility will work.. and maybe even utilize some of the work related to syncing the master key (*Management Improvements/ Master Secret synchronization across instances*) to also sync the signing key when multiple instances are involved. However, this could be work that pushes us over the mid-April target. Thanks... Rob On Fri, Feb 15, 2019 at 10:01 PM Phil Zampino wrote: > Thanks for collecting this comprehensive list of improvements. Many of > these things have been on the “wish list” for a while now, and it would be > great to get them done. > > I’ll see if I can write up some KIP content and/or one-pagers to propose > some details for some of this work. Then we can discuss in more detail, and > define some specific tasks/Jira issues. > > I think shooting for a release mid-April is a good goal, even if we can’t > complete the list exhaustively. > > Thanks again, > Phil > > On Tue, Feb 12, 2019 at 3:51 PM larry mccay wrote: > > > All - > > > > I'd like to officially start the planning for the 1.3.0 release of Apache > > Knox. > > > > After looking at the list of outstanding JIRAs with fixVersion of 1.3.0, > > existing KIPs and considering requirements for a more containerized and > > cloud oriented world, I have a like of general categories: > > > > * TLS Improvements > > - Configurable Keystore Location and Password > > - Configurable Truststore Location and Password > > - Mutual Auth SSL truststores and client certs keystores > > - Dynamic keystore/truststore loading > > * Must keep in mind the KnoxCLI for create-cert, export-cert > > > > * Management Improvements > > There have been a number of people asking about the following and they > are > > all encountering similar pain - whether it be from a containerization > > context, DevOps or management tool, perspective a number of these are > > painful today for Knox admins. > > - Eliminate needs to have access to the Knox machines > > - Bootstrap config for log locations, pids, env variable overrides, > etc > > - Remote access to public certs (for SSL and for various signature > > verification(knoxtoken, knoxsso, etc)) > > - UI for Alias Management > > - Surface logs in UI(maybe?) and API > > - Master Secret synchronization across instances > > - Service Discovery from new source/s > > - new Remote Config Monitor source/s > > - new Remote Alias Service for Vault > > > > * SSO > > Easing the configuration required to enable all of the participating > > applications for KnoxSSO across a deployment will be important in general > > but being able to more easily provision this for cloud deployments will > be > > key. > > - IDP Initiated Flow with Landing Page (Okta portal page) > > - challenge - particpating apps are configured for a single IDP > > - Landing Page is like Okta - with links to UIs - how do we deal > > with multiple topologies > > - KnoxSSOut - logout from landing page > > - Keycloak? > > - Add a standard integration pattern for SPs to register with > KnoxSSO - > > like SAML? > > - Azure AD with OAuth/OpenID Connect > > - Internal hostnames vs external for cookie domain > > - IDP metadata file for SPs to pull KnoxSSO public cert and any other > > details from an endpoint > > > > * Performance > > Performance is an ongoing item but deployment scenarios for cloud and > > hybrid may introduce new strategies for things like load balancing in > front > > of and behind the Knox gateway. > > - LoadBalancing from dispatch > > - HA provider config? > > - service specific > > - Hive cookie - sticky sessions > > - Knox HA story requires sticky sessions > > - TLS Options > > - Sizing Guidelines > > - JVM tuning > > - number of instances based on anticipated load (services need to > > be taken into account) > > > > * KnoxShell > > As deployments move more and more to the cloud and/or hybrid > combinations, > > the need to SSH to a gateway machine becomes more and more awkward. If we > > can provide a powerful enough scripting experience for Data Worker/ETL > type > > roles, we will be able to limit the need to SSH. > > - Remote CLI classes > > - ETL Usecase
[jira] [Work logged] (KNOX-1162) Improve diagnostics for conf/krb5JAASLogin.conf misconfiguration
[
https://issues.apache.org/jira/browse/KNOX-1162?focusedWorklogId=200147=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-200147
]
ASF GitHub Bot logged work on KNOX-1162:
Author: ASF GitHub Bot
Created on: 18/Feb/19 17:24
Start Date: 18/Feb/19 17:24
Worklog Time Spent: 10m
Work Description: rlevas commented on pull request #55: KNOX-1162 -
Logging stacktrace for FATAL messages and displaying a meaningful error message
in case of missing/non-parsable JAAS configuration
URL: https://github.com/apache/knox/pull/55#discussion_r257778724
##
File path:
gateway-service-remoteconfig/src/main/java/org/apache/knox/gateway/service/config/remote/zk/RemoteConfigurationRegistryJAASConfig.java
##
@@ -49,17 +51,26 @@
private static final RemoteConfigurationMessages log =
MessagesFactory.get(RemoteConfigurationMessages.class);
// Cache the current JAAS configuration
-private Configuration delegate = Configuration.getConfiguration();
+private final Configuration delegate;
-private AliasService aliasService;
+private final AliasService aliasService;
-private Map contextEntries = new
HashMap<>();
+private final Map contextEntries = new
HashMap<>();
static RemoteConfigurationRegistryJAASConfig
configure(List configs, AliasService
aliasService) {
return new RemoteConfigurationRegistryJAASConfig(configs,
aliasService);
}
private
RemoteConfigurationRegistryJAASConfig(List
configs, AliasService aliasService) {
+try {
+ delegate = Configuration.getConfiguration();
+} catch(Exception e) {
+ //populate the original error with a meaningful message; logging
will happen later in the upper in the call hierarchy
Review comment:
Change to:
"//populate the original error with a meaningful message; logging will
happen later in the call hierarchy"
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 200147)
Time Spent: 40m (was: 0.5h)
> Improve diagnostics for conf/krb5JAASLogin.conf misconfiguration
>
>
> Key: KNOX-1162
> URL: https://issues.apache.org/jira/browse/KNOX-1162
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
>Affects Versions: 0.14.0
>Reporter: Kevin Minder
>Assignee: Sandor Molnar
>Priority: Minor
> Fix For: 1.3.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When there is a misconfiguration in conf/krb5JAASLogin.conf the server fails
> to start and the information in gateway.log isn't at all helpful. So two
> requests
> # Logging should indicate at a minimum what file contains the issue.
> # All fatal issues should log stack traces without requiring enabling debug
> logging.
> This is the error shown in gateway.log
> {code}
> 2018-01-05 12:05:12,538 FATAL hadoop.gateway (GatewayServer.java:main(163)) -
> Failed to start gateway: java.lang.SecurityException: java.io.IOException:
> Configuration Error:
> Line 7: expected [option key]
> {code}
> When you enabled debug logging you get somewhat better information.
> {code}
> 2018-01-05 15:55:54,087 FATAL hadoop.gateway (GatewayServer.java:main(163)) -
> Failed to start gateway: java.lang.SecurityException: java.io.IOException:
> Configuration Error:
> Line 7: expected [option key]
> java.lang.SecurityException: java.io.IOException: Configuration Error:
> Line 7: expected [option key]
> at sun.security.provider.ConfigFile$Spi.(ConfigFile.java:137)
> at sun.security.provider.ConfigFile.(ConfigFile.java:102)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at
> javax.security.auth.login.Configuration$2.run(Configuration.java:255)
> at
> javax.security.auth.login.Configuration$2.run(Configuration.java:247)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> javax.security.auth.login.Configuration.getConfiguration(Configuration.java:246)
> at
>
[GitHub] rlevas commented on a change in pull request #55: KNOX-1162 - Logging stacktrace for FATAL messages and displaying a meaningful error message in case of missing/non-parsable JAAS configuratio
rlevas commented on a change in pull request #55: KNOX-1162 - Logging
stacktrace for FATAL messages and displaying a meaningful error message in case
of missing/non-parsable JAAS configuration
URL: https://github.com/apache/knox/pull/55#discussion_r257778724
##
File path:
gateway-service-remoteconfig/src/main/java/org/apache/knox/gateway/service/config/remote/zk/RemoteConfigurationRegistryJAASConfig.java
##
@@ -49,17 +51,26 @@
private static final RemoteConfigurationMessages log =
MessagesFactory.get(RemoteConfigurationMessages.class);
// Cache the current JAAS configuration
-private Configuration delegate = Configuration.getConfiguration();
+private final Configuration delegate;
-private AliasService aliasService;
+private final AliasService aliasService;
-private Map contextEntries = new
HashMap<>();
+private final Map contextEntries = new
HashMap<>();
static RemoteConfigurationRegistryJAASConfig
configure(List configs, AliasService
aliasService) {
return new RemoteConfigurationRegistryJAASConfig(configs,
aliasService);
}
private
RemoteConfigurationRegistryJAASConfig(List
configs, AliasService aliasService) {
+try {
+ delegate = Configuration.getConfiguration();
+} catch(Exception e) {
+ //populate the original error with a meaningful message; logging
will happen later in the upper in the call hierarchy
Review comment:
Change to:
"//populate the original error with a meaningful message; logging will
happen later in the call hierarchy"
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Resolved] (KNOX-1759) Improve Github PR Process
[ https://issues.apache.org/jira/browse/KNOX-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden resolved KNOX-1759. Resolution: Fixed Marking as resolved since subtasks completed. Thanks [~smolnar] > Improve Github PR Process > - > > Key: KNOX-1759 > URL: https://issues.apache.org/jira/browse/KNOX-1759 > Project: Apache Knox > Issue Type: Improvement > Components: Build >Reporter: Kevin Risden >Assignee: Sandor Molnar >Priority: Major > Fix For: 1.3.0 > > > After we moved to Gitbox, this enabled the ability to do Github PRs. There > are some rough edges around the integration that we can smooth out. There is > definitely interest based on the knox-dev mailing list thread: > http://mail-archives.apache.org/mod_mbox/knox-dev/201902.mbox/%3CCACRbFygPuEqoKHDzbCB8LAQ-dw%2B8x9Of4TmdP7t7dh_gEmKQ3g%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KNOX-1763) Update committer/contributor documentation with PR process
[ https://issues.apache.org/jira/browse/KNOX-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden resolved KNOX-1763. Resolution: Fixed > Update committer/contributor documentation with PR process > -- > > Key: KNOX-1763 > URL: https://issues.apache.org/jira/browse/KNOX-1763 > Project: Apache Knox > Issue Type: Sub-task >Reporter: Kevin Risden >Assignee: Sandor Molnar >Priority: Major > Fix For: 1.3.0 > > > [https://cwiki.apache.org/confluence/display/KNOX/Contribution+Process] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KNOX-1763) Update committer/contributor documentation with PR process
[ https://issues.apache.org/jira/browse/KNOX-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771206#comment-16771206 ] Kevin Risden commented on KNOX-1763: Changes look good thanks [~smolnar] > Update committer/contributor documentation with PR process > -- > > Key: KNOX-1763 > URL: https://issues.apache.org/jira/browse/KNOX-1763 > Project: Apache Knox > Issue Type: Sub-task >Reporter: Kevin Risden >Assignee: Sandor Molnar >Priority: Major > Fix For: 1.3.0 > > > [https://cwiki.apache.org/confluence/display/KNOX/Contribution+Process] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KNOX-1763) Update committer/contributor documentation with PR process
[ https://issues.apache.org/jira/browse/KNOX-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771046#comment-16771046 ] Sandor Molnar commented on KNOX-1763: - The documentation is now updated: [https://cwiki.apache.org/confluence/display/KNOX/Contribution+Process#ContributionProcess-GithubWorkflow] Pending review from peers. > Update committer/contributor documentation with PR process > -- > > Key: KNOX-1763 > URL: https://issues.apache.org/jira/browse/KNOX-1763 > Project: Apache Knox > Issue Type: Sub-task >Reporter: Kevin Risden >Assignee: Sandor Molnar >Priority: Major > Fix For: 1.3.0 > > > [https://cwiki.apache.org/confluence/display/KNOX/Contribution+Process] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (KNOX-1162) Improve diagnostics for conf/krb5JAASLogin.conf misconfiguration
[
https://issues.apache.org/jira/browse/KNOX-1162?focusedWorklogId=199967=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-199967
]
ASF GitHub Bot logged work on KNOX-1162:
Author: ASF GitHub Bot
Created on: 18/Feb/19 09:23
Start Date: 18/Feb/19 09:23
Worklog Time Spent: 10m
Work Description: smolnar82 commented on issue #55: KNOX-1162 - Logging
stacktrace for FATAL messages and displaying a meaningful error message in case
of missing/non-parsable JAAS configuration
URL: https://github.com/apache/knox/pull/55#issuecomment-464652777
Restart build
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 199967)
Time Spent: 0.5h (was: 20m)
> Improve diagnostics for conf/krb5JAASLogin.conf misconfiguration
>
>
> Key: KNOX-1162
> URL: https://issues.apache.org/jira/browse/KNOX-1162
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
>Affects Versions: 0.14.0
>Reporter: Kevin Minder
>Assignee: Sandor Molnar
>Priority: Minor
> Fix For: 1.3.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When there is a misconfiguration in conf/krb5JAASLogin.conf the server fails
> to start and the information in gateway.log isn't at all helpful. So two
> requests
> # Logging should indicate at a minimum what file contains the issue.
> # All fatal issues should log stack traces without requiring enabling debug
> logging.
> This is the error shown in gateway.log
> {code}
> 2018-01-05 12:05:12,538 FATAL hadoop.gateway (GatewayServer.java:main(163)) -
> Failed to start gateway: java.lang.SecurityException: java.io.IOException:
> Configuration Error:
> Line 7: expected [option key]
> {code}
> When you enabled debug logging you get somewhat better information.
> {code}
> 2018-01-05 15:55:54,087 FATAL hadoop.gateway (GatewayServer.java:main(163)) -
> Failed to start gateway: java.lang.SecurityException: java.io.IOException:
> Configuration Error:
> Line 7: expected [option key]
> java.lang.SecurityException: java.io.IOException: Configuration Error:
> Line 7: expected [option key]
> at sun.security.provider.ConfigFile$Spi.(ConfigFile.java:137)
> at sun.security.provider.ConfigFile.(ConfigFile.java:102)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at
> javax.security.auth.login.Configuration$2.run(Configuration.java:255)
> at
> javax.security.auth.login.Configuration$2.run(Configuration.java:247)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> javax.security.auth.login.Configuration.getConfiguration(Configuration.java:246)
> at
> org.apache.hadoop.gateway.service.config.remote.zk.RemoteConfigurationRegistryJAASConfig.(RemoteConfigurationRegistryJAASConfig.java:52)
> at
> org.apache.hadoop.gateway.service.config.remote.zk.RemoteConfigurationRegistryJAASConfig.configure(RemoteConfigurationRegistryJAASConfig.java:59)
> at
> org.apache.hadoop.gateway.service.config.remote.zk.CuratorClientService.init(CuratorClientService.java:80)
> at
> org.apache.hadoop.gateway.services.DefaultGatewayServices.init(DefaultGatewayServices.java:113)
> at
> org.apache.hadoop.gateway.GatewayServer.main(GatewayServer.java:154)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.gateway.launcher.Invoker.invokeMainMethod(Invoker.java:70)
> at org.apache.hadoop.gateway.launcher.Invoker.invoke(Invoker.java:39)
> at org.apache.hadoop.gateway.launcher.Command.run(Command.java:99)
> at org.apache.hadoop.gateway.launcher.Launcher.run(Launcher.java:69)
> at
[GitHub] smolnar82 commented on issue #55: KNOX-1162 - Logging stacktrace for FATAL messages and displaying a meaningful error message in case of missing/non-parsable JAAS configuration
smolnar82 commented on issue #55: KNOX-1162 - Logging stacktrace for FATAL messages and displaying a meaningful error message in case of missing/non-parsable JAAS configuration URL: https://github.com/apache/knox/pull/55#issuecomment-464652777 Restart build This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
