Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to change Threat Intelligence configuration #53

Closed
joschi opened this issue Sep 26, 2017 · 0 comments
Closed

Unable to change Threat Intelligence configuration #53

joschi opened this issue Sep 26, 2017 · 0 comments
Assignees
Labels
bug
Milestone

Comments

@joschi
Copy link
Contributor

@joschi joschi commented Sep 26, 2017

When trying to change the configuration on the System -> Configuations page, the following exception is thrown:

2017-09-26 15:39:05,896 ERROR: org.graylog2.rest.resources.system.ClusterConfigResource - Couldn't parse cluster configuration "org.graylog.plugins.threatintel.ThreatIntelPluginConfiguration".
com.fasterxml.jackson.databind.JsonMappingException: Can not construct instance of org.graylog.plugins.threatintel.ThreatIntelPluginConfiguration, problem: Null otxApiKey
 at [Source: org.glassfish.jersey.message.internal.EntityInputStream@3018e231; line: 1, column: 95]
	[...]
Caused by: java.lang.NullPointerException: Null otxApiKey
	at org.graylog.plugins.threatintel.AutoValue_ThreatIntelPluginConfiguration$Builder.otxApiKey(AutoValue_ThreatIntelPluginConfiguration.java:119) ~[classes/:?]
	at org.graylog.plugins.threatintel.ThreatIntelPluginConfiguration.create(ThreatIntelPluginConfiguration.java:41) ~[classes/:?]
	[...]
@joschi joschi added the bug label Sep 26, 2017
@joschi joschi added this to the 2.4.0 milestone Sep 26, 2017
joschi pushed a commit that referenced this issue Sep 26, 2017
Jochen Schalanda
Fixes #53
@joschi joschi self-assigned this Sep 26, 2017
@bernd bernd closed this in #54 Sep 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant