# Jakarta Authorization Technology Compatibility Kit, Version 2.0
Release Notes, September 2020

## Kit Contents

The Jakarta Authorization, Version 2.0 Technology Compatibility Kit (TCK) includes the following items:

- Jakarta Authorization TCK tests for signature, API, and End-to-End tests:

- - A signature test checks that all of the public APIs are supported in the Jakarta Authorization Version 2.0 implementation that is being tested

  - API tests for all of the public APIs under the `jakarta.security.jacc` package

  - End-To-End tests that demonstrate compliance with the Jakarta Authorization 2.0 Specification

## Platform Notes

The Jakarta Authorization TCK tests have been built and tested with JavaTM Platform, Standard Edition 8 (Java SE 8).

The Jakarta Authorization TCK tests have been run on the following platforms:

- MAC OS X, El Capitan (10.9.5+)
- Oracle Linux 7.1
- Windows 10
- CentOS Linux 7
- Alpine Linux v3.12

The Jakarta Authorization TCK tests have been run against the Jakarta Authorization 2.0 Compatible Implementation (CI), Eclipse GlassFish 6.0.

Jakarta Enterprise Beans was formerly known as Enterprise Java Beans and abbreviated EJB. References to EJB below refer to Jakarta Enterprise Beans. Use of this term, as commands, switches, or keywords have not been revised.

## Installing, Setting Up, and Running the Jakarta Authorization TCK

Refer to the Jakarta Authorization TCK 2.0 User's Guide for complete instructions on installing, setting up, and running the Jakarta Authorization TCK. The online version of the JT Harness version 5.0 documentation is available here.

## Jakarta Authorization TCK Requirements, Facts, and Figures

The Jakarta Authorization TCK requires a minimum of 103 MB of free disk space:

- Jakarta Authorization TCK (zipped): 23 MB
- Jakarta Authorization TCK (unzipped): 79 MB
- Space for Jakarta Authorization log/report files: 1 MB minimum

The test suite bundle contains the following:

- EARs: 0
- JARs: 41
- WARs: 6
- Total tests: 32
  - Web Container: 23
  - EJB-lite: 9
  - EJB Container: n/a (Jakarta Enterprise Beans Container tests are only available in full CTS 8)

There are multiple levels of compliance available for Jakarta Authorization certification. Jakarta Authorization allows for certification of the following containers: Web Container, Jakarta Enterprise Beans Container, or Both. The standalone Jakarta Authorization TCK only concerns itself with Web Container tests and possibly some Jakarta Enterprise Beans-lite tests (which could be run in a Web Profile environment). There are keywords available which can be supplied on the command line which allow isolating the tests for a given level of certification. (For more on keywords, see the Jakarta Authorization 2.0 TCK User Guide). The list of keywords available for Jakarta Authorization 2.0 TCK is as follows:

- keyword jacc_web : used to run Web Container tests
- keyword jacc_ejb : used to run Jakarta Enterprise Beans Container tests
- keyword jacc_web_profile : used to run WEB and Jakarta Enterprise Beans Lite Container tests in Web Profile environment
- keyword jacc : used to run all Jakarta Authorization standalone TCK tests

## Status Information

### Exclude List

> You can find the exclude list in the Jakarta Authorization bundle in `<TS_HOME>/bin/ts.jtx`. Since the list can change over time, please be sure to get the latest exclude list from the Jakarta Authorization Specification Web site: https://jakarta.ee/specifications/authorization/2.0/.

## Known Problems and Workarounds

### Running the Jakarta Authorization TCK Against Jakara EE compatible implementation on Windows

> When configuring and running the Jakarta Authorization TCK against the CI on Windows, please make sure to install all related software (Java SE 8, the CI, the Jakarta Authorization TCK, etc.) on the same drive (for example, `C:`). If you want to install on a drive other than `C:`, please be sure to change the following properties in `<TS_HOME>/bin/ts.jte:`

>     s1as.applicationRoot=c: