This enhancement enables the use of the previously internal knox.id as a Passcode Token for accessing proxied resources as an Authorization Bearer token or HTTP Basic password. This id has been used to bind incoming KnoxTokens (JWT) that embed such an id to the metadata in the Token State Server in order to provide server side state management.
The motivation for this is the fact that certain 3rd party BI tooling such as tableau not only have the inability to set a bearer token but also have size limitations on the password field used to collect the username and password credentials.
We will need to enhance the current JWTProvider to not require an actual JWT but the Passcode Token will represent the same backend metadata.
This does mean that Passcode Tokens can only be used with the Token State Server functionality enabled for both the KnoxToken service and the JWTProvider federation provider.