I copied correct oids from dsee schema, but some are still missing:

nsTLS1-oid
nsTLS10-oid
nsTLS11-oid
nsTLS12-oid
sslVersionMin-oid
sslVersionMax-oid
nsSSLSupportedCiphers-oid
allowWeakCipher-oid
CACertExtractFile-oid
nsTLSAllowClientRenegotiation-oid
ServerKeyExtractFile-oid
ServerCertExtractFile-oid
nsmsgNumMsgQuota-oid

They were added much later, than in dsee.

We can generate our own OID's for these @vashirov if that helps?

Otherwise, ack to this

Ack as well, and like @firstyear said we can just create new OIDs from our internal OID list.

@mreynolds As a general point of order, I can no longer touch the RH oids list, so is it possible to have the rhanana components related to 389ds opensourced into our repo since we are the only user of that subset of OIDS?

Looks good to me too. Probably, we can merge it after one more rebase (and one more test run, just to be sure)

Just as a reminder, I still don't have access to the RH numbers authority anymore, but I'll need to assign OID's for schema so we need a way to fix this. Either we need the OID segment that RH controls delegated such that the authority is stored in the 389 repo, or we need to get a new prefix assigned that we control as a project ....

@mreynolds As a general point of order, I can no longer touch the RH oids list, so is it possible to have the rhanana components related to 389ds opensourced into our repo since we are the only user of that subset of OIDS?

The related components are already opensourced and are present in schema. There are no "secret" OIDs. We're not the only one user of the allocated subset, there is also FreeIPA.

Just as a reminder, I still don't have access to the RH numbers authority anymore, but I'll need to assign OID's for schema so we need a way to fix this. Either we need the OID segment that RH controls delegated such that the authority is stored in the 389 repo, or we need to get a new prefix assigned that we control as a project ....

If you need to assign OIDs, please reach out to Mark or someone from the team, and we will gladly facilitate you.

I will open a separate PR for the remaining OIDs.

@mreynolds As a general point of order, I can no longer touch the RH oids list, so is it possible to have the rhanana components related to 389ds opensourced into our repo since we are the only user of that subset of OIDS?

The related components are already opensourced and are present in schema. There are no "secret" OIDs. We're not the only one user of the allocated subset, there is also FreeIPA.

I'm not saying it's secret at all - I just know that the master list of OID's is in a private RH-only git repo, so I can't modify it.

Just as a reminder, I still don't have access to the RH numbers authority anymore, but I'll need to assign OID's for schema so we need a way to fix this. Either we need the OID segment that RH controls delegated such that the authority is stored in the 389 repo, or we need to get a new prefix assigned that we control as a project ....

If you need to assign OIDs, please reach out to Mark or someone from the team, and we will gladly facilitate you.

I think what I'm saying is from a community and upstream collaboration point of view, the master-file of OID assignments should be part of the 389 project git rather than a private-RH-only git repo so that I don't need to ask you to facilitate. However, it's up to people within Red Hat to communicate with management to get that segment from RHANA moved to the 389 project, or, the 389 project should get it's own OID space so that we can have an upstream-first approach to allocations.

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3020

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.