Skip to content
This repository was archived by the owner on Jul 12, 2023. It is now read-only.

API key for one realms returns signing configuration for a different realm #397

Closed
sherifkozman opened this issue Aug 27, 2020 · 1 comment · Fixed by #398
Closed

API key for one realms returns signing configuration for a different realm #397

sherifkozman opened this issue Aug 27, 2020 · 1 comment · Fixed by #398
Assignees
@mikehelmick
Labels
kind/bug Something is malfunctioning.

Comments

@sherifkozman
Copy link
Contributor

We noticed that using an API Key for a specific realm (i.e 3) returns signing confguration of a different realm (i.e7) , specifically the last realm that was created, causing mismatch in our workflow.

@mikehelmick
@sherifkozman sherifkozman added the kind/bug Something is malfunctioning. label Aug 27, 2020
@mikehelmick
Copy link
Contributor

/assign

@mikehelmick mikehelmick mentioned this issue Aug 27, 2020
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mikehelmick mikehelmick

Labels
kind/bug Something is malfunctioning.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

scope signing key read to selected realm mikehelmick/exposure-notifications-verification-server
2 participants
@mikehelmick @sherifkozman