INTERNAL - Perpetual License Validity for OP5 Monitoring

Introduction

This report investigates a discrepancy between the maximum (perpetual) license validity allowed for OP5 Monitoring as stated in Atlassian documentation and the observed behavior within the middleware.

Findings

• Atlassian Documentation: The license creation instruction pages within Atlassian state that the maximum validity for generated OP5 Monitoring licenses is 36 months.
  Links to the mentioned documentation:
  
  • https://itrs.atlassian.net/wiki/spaces/support/pages/1924255448/OP5+Monitor+Licence+Creation
  • https://itrs.atlassian.net/wiki/spaces/support/pages/1924202573/License+Generation+Instructions
• Middleware Behavior: Testing and analysis have revealed that the middleware can generate OP5 licenses with a maximum validity of up to 37 months.
  
  • IIP ticket for the testing done for this behavior is found in this link: https://itrs.zendesk.com/agent/tickets/372700

Impact

This discrepancy may have the following implications:

• Potential for Extended License Coverage: The ability to generate licenses with a 37-month validity provides an additional month of coverage compared to the documented limit. This could be beneficial for planning and license management.
• Compliance Considerations: It's crucial to ensure compliance with OP5 licensing terms and conditions. Further investigation is required to determine if generating 37-month licenses is within the acceptable range or if it constitutes a deviation from the licensing policy and agreement.
• Documentation Accuracy: The discrepancy highlights a potential inaccuracy in the Atlassian documentation.

Recommended actions

• Documentation Update: If generating 37-month licenses is confirmed to be permissible, recommend updating the Atlassian documentation to reflect the accurate maximum validity.
• Internal Communication: Communicate the findings and any subsequent clarifications from relevant teams to ensure consistent understanding and adherence to licensing policies.