Skip to content

Conversation

@rakhimundhada15
Copy link
Contributor

Description

  1. Cisco Meraki has announced that requests to unsupported base URIs will start to fail on November 17, 2025. Start using standard base ENG-59388.
  2. Cisco Meraki Dashboard API v1 now supports Bearer Authentication using the standard Authorization header.ENG-59370]
  3. Cisco Meraki API Collector Failing with Double Slash in https://api.meraki.com. Refer ENG-59371

Solution Description

  1. Added the condition to check if customer provided end point is start with api then use the same else use the standard api.meraki.com instated of user specific URI like n219.meraki.com.
  2. Update the authorisation process to supports Bearer Authentication now onwards as per Cisco document
  3. Removed the extra slash to fix the issue.

@rakhimundhada15 rakhimundhada15 changed the title [Cisco Meraki] : Update the Authorisation and base URI [Cisco Meraki] : Update the Authorisation and supported base URI Oct 30, 2025
@al-cibot
Copy link

CI Service Job Number 1124 Logs - SUCCESS

alps ci job-logs --organization alertlogic --repository paws-collector --job-num 1124 -g

Stages Run:

  • PR Test

@al-cibot
Copy link

CI Service Job Number 1125 Logs - SUCCESS

alps ci job-logs --organization alertlogic --repository paws-collector --job-num 1125 -g

Stages Run:

  • PR Test

@rakhimundhada15
Copy link
Contributor Author

build-collector-ciscomeraki

1 similar comment
@rakhimundhada15
Copy link
Contributor Author

build-collector-ciscomeraki

@al-cibot
Copy link

al-cibot commented Nov 3, 2025

CI Service Job Number 1126 Logs - SUCCESS

alps ci job-logs --organization alertlogic --repository paws-collector --job-num 1126 -g

Stages Run:

  • build-collector-ciscomeraki
  • file_packager_16dd7c

@rakhimundhada15 rakhimundhada15 merged commit 8125fbb into alertlogic:master Nov 3, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants