Prepare keys for environment migration

[MarceloRGonc]

Part of OPS-3849.

[linear]

OPS-3849 Migrate Frontegg Production environment to Development environment

[Copilot]

Pull request overview

This PR prepares for an environment migration by adding support for an old Frontegg public key (OLD_FRONTEGG_PUBLIC_KEY) alongside the current one. During migration, JWT tokens signed with either the old or new key will be accepted, ensuring continuity for authenticated users.

Changes:

• Added OLD_FRONTEGG_PUBLIC_KEY to the AppSystemProp enum for system configuration.
• Updated both user-info.module.ts and cloud-template.controller.ts to try verifying JWTs against both the new and old public keys (falling back to the old key if the new one fails).
• Introduced a new verifyUserWithPublicKeys helper function (duplicated in both files) that iterates over an array of keys.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
packages/server/shared/src/lib/system/system-prop.ts	Added OLD_FRONTEGG_PUBLIC_KEY enum value
packages/server/api/src/app/user-info/user-info.module.ts	Updated auth to try multiple public keys; added verifyUserWithPublicKeys
packages/server/api/src/app/flow-template/cloud-template.controller.ts	Updated auth to try multiple public keys; added duplicate verifyUserWithPublicKeys

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[MarceloRGonc]

The expiration date for these tokens is 1 month. Therefore, we must keep the old tokens valid for at least 1 month.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
1 Accepted issue

Measures
0 Security Hotspots
0.0% Coverage on New Code
15.0% Duplication on New Code

See analysis details on SonarQube Cloud