Invalid CSR while onboarding on production

Onboarding, renewal and revocation
1

Please consider it Urgent as we have to move on production tommorow @idaoud
Dear Zatca Team,
I dont know why each and every single time i have to face the same issue of Invalid CSR due to different resaons everytime i try to onboard
i did onbaording 3 months ago at that time i faced this issue and before this i faced it as well
Each and every time i onboard any solution i dont knowWhy .Please review

this is my .cnf file details

oid_section = OIDs
[OIDs]
certificateTemplateName = 1.3.6.1.4.1.311.20.2
[req]
default_bits = 2048
emailAddress = mail@xx.com.sa
req_extensions = v3_req
x509_extensions = v3_ca
prompt = no
default_md = sha 256
req_extensions = req_ext
distinguished_name = dn
[dn]
C=SA
OU=3109xxxx
O= Company xxx
CN=10106xxxxx
[v3_req]
basicConstraints = CA:FALSE
keyUsage = digitalSignature,nonRepudiation,keyEncipherment
[req_ext]
certificateTemplateName = ASN1:PRINTABLESTRING:ZATCA-Code-Signing
subjectAltName = dirName:alt_names
[alt_names]
SN=1-GRN|2-MCT|3-a6bc16f3-9bd6-4612-a4ce-17415e46ea4d
UID=31090444xxxxx
title=1100
registeredAddress=Riyadh,Saudi Arabia
businessCategory=Consumer Goods

and these are the commands i am using

1- Create private key

openssl ecparam -name secp256k1 -genkey -noout -out ec-secp256k1-priv-key.pem

2- Create public key

openssl ec -in ec-secp256k1-priv-key.pem -pubout > ec-secp256k1-pub-key.pem

3- Create CSR

openssl req -new -sha256 -key ec-secp256k1-priv-key.pem -extensions v3_req -config config.cnf -out my.csr

2

Try This:

[ req ]
prompt = no
utf8 = yes
distinguished_name = my_req_dn_prompt
req_extensions  = v3_req
[ v3_req ]
1.3.6.1.4.1.311.20.2 = ASN1:PRINTABLESTRING:ZATCA-Code-Signing
subjectAltName=dirName:dir_sect

[ dir_sect ]
SN = 1-GRN|2-MCT|3-a6bc16f3-9bd6-4612-a4ce-17415e46ea4d
UID =3109xxxx
title = 1100
registeredAddress = Riyadh
businessCategory = Consumer Goods
[my_req_dn_prompt]
commonName = 10106xxxxx
organizationalUnitName = 10106xxxxx
organizationName = Company xxx
countryName = SA

For the common name, you can enter anything unique that will help you identify EGS in EGSs list on the Fatoora platform.

For the organizationalUnitName, it’s best if its value matches the CRN from which the electronic tax invoices will be issued. If the taxpayer is a VAT Group, then 10 digit TIN must be entered. Otherwise, you can enter either name of the branch or CRN of the branch.

The taxpayer is a VAT Group if 11th digit of the VAT Number is equal to 1

3

Not working still same error of invalid csr