Support session tokens and non-JSON responses for license checks.

Review Request #14613 — Created Sept. 14, 2025 and submitted

Information

Review Board
release-7.1.x

Reviewers

When preparing for a license check on the Licenses page, a License
Provider can now provide a Session Token, which is an opaque value that
will be passed back during processing of a response. That allows
information to be temporarily stored and then retrieved for response
processing.

Responses are also no longer required to be JSON. A license server may
now provide any kind of text-based response, which may be processed by
the License Provider however needed.

Unit tests pass.

Tested this with the in-progress work in Power Pack.

Summary ID
Support session tokens and non-JSON responses for license checks.
When preparing for a license check on the Licenses page, a License Provider can now provide a Session Token, which is an opaque value that will be passed back during processing of a response. That allows information to be temporarily stored and then retrieved for response processing. Responses are also no longer required to be JSON. A license server may now provide any kind of text-based response, which may be processed by the License Provider however needed.
9f63025340821609c03b18c99ccd6751013ac4ce
Description From Last Updated

Given that content-type headers can include other info like charsets, and are not case sensitive, we probably should do something …

daviddavid
david
  1. 
      
  2. Show all issues

    Given that content-type headers can include other info like charsets, and are not case sensitive, we probably should do something like:

    const contentType = response.headers['content-type'].toLowerCase()
    
    if (contentType.includes('application/json') {
    
  3. 
      
chipx86
david
  1. Ship It!
  2. 
      
chipx86
Review request changed
Status:
Completed
Change Summary:
Pushed to release-7.1.x (433a1ec)