Skip to content

cisco_duo: include error response body when non-200 and fix next_offset handling - #11422

Merged
chrisberkhout merged 2 commits into
elastic:mainfrom
efd6:s5272-cisco_duo
Oct 16, 2024
Merged

cisco_duo: include error response body when non-200 and fix next_offset handling#11422
chrisberkhout merged 2 commits into
elastic:mainfrom
efd6:s5272-cisco_duo

Conversation

@efd6

@efd6 efd6 commented Oct 15, 2024

Copy link
Copy Markdown
Contributor

Proposed commit message

We cannot guarantee the shape of body.message and body.message_detail, so just
include the known type resp.Body which should be short in the case of a
non-200 response.

The next_offset value is documented to be an array of two elements which must
be used to construct the parameter by concatenation with a separating comma[1].

[1]https://duo.com/docs/adminapi#authentication-logs

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@efd6 efd6 added Integration:cisco_duo Cisco Duo bugfix Pull request that fixes a bug issue Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] labels Oct 15, 2024
@efd6 efd6 self-assigned this Oct 15, 2024
We cannot guarantee the shape of body.message and body.message_detail,
so just include the known type resp.Body which should be short in the
case of a non-200 response.
@elastic-vault-github-plugin-prod

elastic-vault-github-plugin-prod Bot commented Oct 15, 2024

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@efd6
efd6 marked this pull request as ready for review October 15, 2024 22:42
@efd6
efd6 requested a review from a team as a code owner October 15, 2024 22:42
@elasticmachine

Copy link
Copy Markdown

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@efd6 efd6 changed the title cisco_duo: include error response body when non-200 Oct 16, 2024
@elasticmachine

Copy link
Copy Markdown

💚 Build Succeeded

History

cc @efd6

@chrisberkhout
chrisberkhout merged commit aa7ee7e into elastic:main Oct 16, 2024
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Package cisco_duo - 2.0.2 containing this change is available at https://epr.elastic.co/search?package=cisco_duo

harnish-crest-data pushed a commit to chavdaharnish/integrations that referenced this pull request Feb 4, 2025
…et handling (elastic#11422)

We cannot guarantee the shape of body.message and body.message_detail, so just
include the known type resp.Body which should be short in the case of a
non-200 response.

The next_offset value is documented to be an array of two elements which must
be used to construct the parameter by concatenation with a separating comma[1].

[1] https://duo.com/docs/adminapi#authentication-logs
harnish-crest-data pushed a commit to chavdaharnish/integrations that referenced this pull request Feb 5, 2025
…et handling (elastic#11422)

We cannot guarantee the shape of body.message and body.message_detail, so just
include the known type resp.Body which should be short in the case of a
non-200 response.

The next_offset value is documented to be an array of two elements which must
be used to construct the parameter by concatenation with a separating comma[1].

[1] https://duo.com/docs/adminapi#authentication-logs
@efd6
efd6 deleted the s5272-cisco_duo branch February 5, 2025 22:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Pull request that fixes a bug issue Integration:cisco_duo Cisco Duo Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

3 participants