CCM-12615: APIM Authentication#116
Merged
simonlabarere merged 5 commits intomainfrom Nov 24, 2025
Merged
Conversation
5830910 to
39af95d
Compare
Contributor
gareth-allan
left a comment
There was a problem hiding this comment.
Some minor comments from a look through the TF changes. I still need to look over the actual lambda code.
sidnhs
approved these changes
Nov 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
APIM Key generation / rotation + token generation.
Context
Testing
Developer portal updated to make the APIM application point at the the public key of this PR
Private and Public keys generated by the key-generation lambda
Public key exposed using Cloudfront
Auth token generated by the refresh-apim-access-token lambda
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.