Error when trying to add an additional Office 365 input

Graylog Central (peer support)
1

1. Describe your incident:
Getting the following error on the portal when trying to add an additional Office365 input at the content subscription page:

Cannot invoke “java.util.List.stream()” because the return value of “org.graylog.enterprise.integrations.office365.external.O365Client.getSubscriptions()” is null.

Tested on another Office 365 tenant, same issue - We’ve previously added many others without issue

2. Describe your environment:

Self-Hosted Linux (ubuntu) (single instance) - Graylog Enterprise Server version 4.3.7-1. Was on previous version, updated to latest as part of troubleshooting

  • OS Information:

Ubuntu 18.4.6

  • Package Version:
    raylog Enterprise Server version 4.3.7-1

  • Service logs, configurations, and environment variables:
    No errors on the portal besides the listed one when adding an additional input

3. What steps have you already taken to try and solve the problem?

4. How can the community help?

Helpful Posting Tips: Tips for Posting Questions that Get Answers [Hold down CTRL and link on link to open tips documents in a separate tab]

2

Hello,

Using this type of input here I believe you need Graylog License. I would contact Graylog support here about this. It may have something to do with the license.

3

Thanks, we have Graylog Enterprise license with the portal saying no license issues. There’s some license check failures, but have verified that the Graylog box can reach the API

4

Understood, I would reach out to Graylog Support about this since you have a license.

5

Thanks, have now done so

1 Like
6

Support has stated that the license doesn’t qualify for support, so I’m reaching out to the community. Does anyone have any suggestions as to how to resolve this, or where to start looking?

The license we have (open source) does qualify for the Office 365 plugin, and we have many tenants already connected… It’s just when adding new ones it fails. Thanks in advance

7

This reads to me as something is wrong in the settings on the Azure configuration side - perhaps with permissions - you have gone over your process with the docs? with client applications permissions specifically and enabling unified Audit Logging?

1 Like
8

Thanks. I’ve tried again with the tenant and it looks like it’s working now… Perhaps it just needed more time? Unified logging was enabled just prior to adding the input, so perhaps it takes more than an hour. Anyway, it’s working and looks like it was just about waiting for time.

Thanks everyone

2 Likes
9

Great!! Maybe just jostling it a bit loosened up a couple of fouled bits… :stuck_out_tongue:

10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.