[
https://issues.apache.org/jira/browse/KNOX-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-2874:
--------------------------------
+Apache Knox 3.0.0 release preparation+
We are about to cut the 3.0.0 release branch. master will move on to 3.1.0.
This issue is currently unresolved and is not automatically included in 3.0.0.
Please choose one of the following:
# If this belongs in 3.0.0: once the branch is cut, cherry-pick your commit(s)
onto the new v3.0.0 branch in addition to master. Leave Fix Version = 3.0.0 so
we can track it.
# Do nothing: we will move this issue to the next release (3.1.0) as part of
release cleanup.
If we don't hear back and see no cherry-pick, the issue will be re-targeted to
3.1.0. Thanks!
> 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: 3.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)
