[
https://issues.apache.org/jira/browse/KNOX-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Han updated KNOX-3346:
----------------------------
Description:
While implementing a new custom LDAP control for the internal Knox LDAP server
(see KNOX-3340), the need for an official Object Identifier (OID) was
identified.
Currently, the implementation is using a UUID-generated OID appended to the
Apache Private Enterprise Number (PEN) 1.3.6.1.4.1.18060. While this ensures
uniqueness, it is non-idiomatic for a top-level project and results in
extremely long identifiers that are difficult to manage in configuration and
CLI tools.
As discussed in the [PR
review|https://github.com/apache/knox/pull/1258#discussion_r3394424270], we
should secure an official sub-arc for the Knox project under the ASF PEN
(18060) to provide a professional and permanent space for Knox-specific LDAP
controls, attributes, and object classes.
{*}Proposed Action for PMC Chair:{*}{*}{{*}}
Please open an INFRA JIRA ticket to request the assignment of a dedicated OID
sub-arc for the Apache Knox project under the root 1.3.6.1.4.1.18060.
was:
While implementing a new custom LDAP control for the internal Knox LDAP server
(see KNOX-1340), the need for an official Object Identifier (OID) was
identified.
Currently, the implementation is using a UUID-generated OID appended to the
Apache Private Enterprise Number (PEN) 1.3.6.1.4.1.18060. While this ensures
uniqueness, it is non-idiomatic for a top-level project and results in
extremely long identifiers that are difficult to manage in configuration and
CLI tools.
As discussed in the [PR
review|https://github.com/apache/knox/pull/1258#discussion_r3394424270], we
should secure an official sub-arc for the Knox project under the ASF PEN
(18060) to provide a professional and permanent space for Knox-specific LDAP
controls, attributes, and object classes.
{*}Proposed Action for PMC Chair:{*}{*}{*}
Please open an INFRA JIRA ticket to request the assignment of a dedicated OID
sub-arc for the Apache Knox project under the root 1.3.6.1.4.1.18060.
> Request official OID sub-arc assignment for Apache Knox from ASF INFRA
> ----------------------------------------------------------------------
>
> Key: KNOX-3346
> URL: https://issues.apache.org/jira/browse/KNOX-3346
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Sandor Molnar
> Assignee: Larry McCay
> Priority: Major
>
> While implementing a new custom LDAP control for the internal Knox LDAP
> server (see KNOX-3340), the need for an official Object Identifier (OID) was
> identified.
> Currently, the implementation is using a UUID-generated OID appended to the
> Apache Private Enterprise Number (PEN) 1.3.6.1.4.1.18060. While this ensures
> uniqueness, it is non-idiomatic for a top-level project and results in
> extremely long identifiers that are difficult to manage in configuration and
> CLI tools.
> As discussed in the [PR
> review|https://github.com/apache/knox/pull/1258#discussion_r3394424270], we
> should secure an official sub-arc for the Knox project under the ASF PEN
> (18060) to provide a professional and permanent space for Knox-specific LDAP
> controls, attributes, and object classes.
> {*}Proposed Action for PMC Chair:{*}{*}{{*}}
> Please open an INFRA JIRA ticket to request the assignment of a dedicated OID
> sub-arc for the Apache Knox project under the root 1.3.6.1.4.1.18060.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
