Oracle Cloud Infrastructure Documentation

Tokens

The Tokens tab lists all the tokens generated in the tenancy region along with its details. Java Download relies on Tokens to enable script friendly download commands.

Tokens are associated with each download command and are generated for each Java version by, if applicable, accepting the license terms so that it can be distributed to non-OCI users in the enterprise. As the token is already associated with a Java version and license acceptance, any user can use them to download Java without additional license acceptance or entitlement checks.

You can generate new tokens and manage the existing tokens. For each token, the table presents the following information:

  • Name: name of the token; token description can be viewed as a tooltip next to the name.
  • State: state of the token such as:
    • Active: this token is active and can be used in script friendly download commands
    • Expired: this token's expiry date has passed and it can no longer be used in script friendly download commands
    • Revoked: this token was revoked by an user and can no longer be used in script friendly download commands
  • Value: the alphanumeric token value generated by Java download for the corresponding token. You can view or copy the value.
  • Java version: associated Java version for which the token is generated
  • License type: associated license type such as OTN or NFTC
  • Expiry: the expiry date of the token
  • Created by: the user who created the token
  • Updated by: the user who last updated the token
  • Created: the date of token creation
  • Last updated: the date when the token was last updated

Actions

You can perform the following actions:
  • Generate New Token
  • Each row of the table includes a contextual menu indicated by a vertical ellipsis (⋮). From this menu you can:
  • Search for a particular token by entering the token value in the Search field.

Token Expiry

The token expiry date is calculated based on:
  • JDK version
  • EOSL date of the JDK version
  • License type
The following table provides the expiry date calculation based on these parameters.

Table 4-1 Token Expiry Date

Version Type Max Expiry Date Default Expiry Date Calculation

LTS versions - JDK 8 and 11, and non-LTS versions

EOSL date + 2 years

For supported versions: EOSL date of the JDK version

For unsupported versions: Earliest of (Date of token generation + 1 month) and Max Expiry Date

LTS versions other than JDK 8 and 11, during the first 3 years of release (New releases are under NFTC license)

NFTC validity + 2 years

After the last release of the version under NFTC license terms, you will have the option to extend the expiry date beyond the version's EOSL date by accepting OTN license terms. See the next row for details.

If OTN license terms are not accepted, only releases under NFTC license will be available using the token.

NFTC validity date - Last day of the month, 3 years from the release date of the version

LTS versions, other than JDK 8 and 11, after the first 3 years of release (New releases are under OTN license)
  • If OTN license is accepted: EOSL date + 2 years

    Releases under OTN and NFTC license will be available using this token.

  • If OTN license is not accepted: NFTC validity + 2 years

    Releases under OTN license will not be available using this token.
  • If OTN license is accepted: EOSL date of version
  • If OTN license is not accepted:
    • New token: Earliest of (Date of token generation + 1 month) and max expiry date
    • Extending existing token:

      Token not expired: Existing expiry date

      Token expired: Earliest of (Date of token generation + 1 month) and max expiry date