Skip to content

CyrenThreatIntelligence v3.0.4: Optional tokens with conditional deployment#13811

Merged
v-atulyadav merged 1 commit into
Azure:masterfrom
Data443:feature/cyren-v3.0.4-optional-tokens
Mar 13, 2026
Merged

CyrenThreatIntelligence v3.0.4: Optional tokens with conditional deployment#13811
v-atulyadav merged 1 commit into
Azure:masterfrom
Data443:feature/cyren-v3.0.4-optional-tokens

Conversation

@mazamizo21
Copy link
Copy Markdown
Contributor

Summary

Made both JWT tokens (IP Reputation and Malware URL) optional with ARM conditional deployment. Customers can now install either feed or both based on their subscription.

Changes

  • Changed minLength: 1 to minLength: 0 for both token parameters
  • Added ARM conditions to each RestApiPoller connector:
    • IP Reputation: "condition": "[not(empty(parameters('cyrenIpReputationToken')))]"
    • Malware URL: "condition": "[not(empty(parameters('cyrenMalwareUrlToken')))]"
  • Updated UI labels to indicate tokens are "(Optional)"
  • Updated placeholder text to "Leave empty if not purchased"
  • Added instruction text: "You can use either feed or both depending on your subscription. Leave the token field empty for any feed you have not purchased — only the connectors for provided tokens will be deployed."

Why

Cyren feeds are now sold separately on Azure Marketplace as individual SaaS offers (IP Reputation and Malware URL). Customers purchasing only one feed were unable to deploy without entering a dummy token for the other feed, which caused:

  1. ARM template validation errors (minLength constraint)
  2. 403 errors on the unused connector when a dummy token was entered

This fix allows flexible deployment matching the subscription model.

Files Changed

  • Solutions/CyrenThreatIntelligence/Package/mainTemplate.json - Added conditions and updated UI text
  • Solutions/CyrenThreatIntelligence/Package/3.0.4.zip - Updated package
  • Solutions/CyrenThreatIntelligence/ReleaseNotes.md - Added v3.0.4 entry

Testing

  • ARM template validation passed ✅
  • JSON syntax validation passed ✅
  • Solution deployment to test workspace succeeded ✅

…oyment

## Summary
Made both JWT tokens (IP Reputation and Malware URL) optional with ARM conditional deployment. Customers can now install either feed or both based on their subscription.

## Changes
- Changed `minLength: 1` to `minLength: 0` for both token parameters
- Added ARM conditions to each RestApiPoller connector:
  - IP Reputation: `"condition": "[[not(empty(parameters('cyrenIpReputationToken')))]"`
  - Malware URL: `"condition": "[[not(empty(parameters('cyrenMalwareUrlToken')))]"`
- Updated UI labels to indicate tokens are optional
- Updated placeholder text to "Leave empty if not purchased"
- Added instruction text explaining customers can use either feed or both

## Why
Cyren feeds are now sold separately on Azure Marketplace. Customers purchasing only one feed were unable to deploy without entering a dummy token, which caused 403 errors on the unused connector. This fix allows flexible deployment matching the subscription model.
@mazamizo21 mazamizo21 requested review from a team as code owners March 12, 2026 20:30
@v-shukore v-shukore self-assigned this Mar 13, 2026
@v-shukore v-shukore added the Solution Solution specialty review needed label Mar 13, 2026
@v-atulyadav v-atulyadav merged commit e198cdb into Azure:master Mar 13, 2026
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Solution Solution specialty review needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants