[
https://issues.apache.org/jira/browse/KNOX-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Zampino updated KNOX-2874:
---------------------------------
Description:
There are actually six occurrences of the following characters through the User
Guide.
{noformat}
’{noformat}
{noformat}
If you want to use the newly implemented database token management, you’ve to
set gateway.service.tokenstate.impl in gateway-site.xml to
org.apache.knox.gateway.services.token.impl.JDBCTokenStateService.{noformat}
{noformat}
If your database requires user/password authentication, the following aliases
must be saved into the Knox Gateway’s credential store
(__gateway-credentials.jceks):{noformat}
{noformat}
JWT token - this is the serialized JWT and is fully compatible with the
old-style Bearer authorization method. Clicking the JWT Token label on the page
will copy the value into the clipboard. You might want to use it as the
‘Token’ user:{noformat}
{noformat}
Passcode token - this is the serialized passcode token, which you can use as
the ‘Passcode’ user (Clicking the Passcode Token label on the page will
copy the value into the clipboard):{noformat}
{noformat}
REMOVE_OLDEST - if that’s configured, the oldest token of the user, who the
token is being generated for, will be removed{noformat}
{noformat}
RETURN_ERROR - if that’s configured, Knox will return an error response with
403 error code (as it did in previous versions){noformat}
was:
{noformat}
If you want to use the newly implemented database token management, you’ve to
set gateway.service.tokenstate.impl in gateway-site.xml to
org.apache.knox.gateway.services.token.impl.JDBCTokenStateService.{noformat}
{noformat}
If your database requires user/password authentication, the following aliases
must be saved into the Knox Gateway’s credential store
(__gateway-credentials.jceks):{noformat}
> Typos in JDBC token state service config docs
> ---------------------------------------------
>
> Key: KNOX-2874
> URL: https://issues.apache.org/jira/browse/KNOX-2874
> Project: Apache Knox
> Issue Type: Improvement
> Components: Document
> Affects Versions: 2.0.0
> Reporter: Philip Zampino
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 2.0.0
>
>
> There are actually six occurrences of the following characters through the
> User Guide.
> {noformat}
> ’{noformat}
> {noformat}
> If you want to use the newly implemented database token management, you’ve
> to set gateway.service.tokenstate.impl in gateway-site.xml to
> org.apache.knox.gateway.services.token.impl.JDBCTokenStateService.{noformat}
>
> {noformat}
> If your database requires user/password authentication, the following aliases
> must be saved into the Knox Gateway’s credential store
> (__gateway-credentials.jceks):{noformat}
>
> {noformat}
> JWT token - this is the serialized JWT and is fully compatible with the
> old-style Bearer authorization method. Clicking the JWT Token label on the
> page will copy the value into the clipboard. You might want to use it as the
> ‘Token’ user:{noformat}
> {noformat}
> Passcode token - this is the serialized passcode token, which you can use as
> the ‘Passcode’ user (Clicking the Passcode Token label on the page will
> copy the value into the clipboard):{noformat}
> {noformat}
> REMOVE_OLDEST - if that’s configured, the oldest token of the user, who the
> token is being generated for, will be removed{noformat}
> {noformat}
> RETURN_ERROR - if that’s configured, Knox will return an error response
> with 403 error code (as it did in previous versions){noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
