italia / italia/spid-compliant-certificates-python

Errori di validazione con SPID Validator: SubjectDN must contain name attribute [organizationIdentifier, 2.5.4.97]

Open
#140 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
25
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Salve,
abbiamo generato il certificato con questo tool e lo abbiamo inserito nella nostra installazione Keycloak per firmare il metadata. Abbiamo effettuato il test con https://demo.spid.gov.it/, ma il risultato del Demo SPID diverge da quello del validator incluso con questo tool.

```
spid-compliant-certificates generator \
--key-size 2048 \
--common-name "https://sso.aspbassaromagna.it" \
--days 3650 \
--entity-id "https://www.aspbassaromagna.it" \
--locality-name "Bagnacavallo" \
--org-id "PA:IT-adcbr" \
--org-name "ASP dei Comuni della Bassa Romagna" \
--sector public

```
Risultato validazione (`spid-compliant-certificates validator --sector public`)
![image](https://user-images.githubusercontent.com/59199289/206143877-c64dc245-ec81-4b2b-b0c1-5703a8c7004f.png)

Risultato SPID Validator - 1.9.2, SPID SP Test - 1.2.5
![image](https://user-images.githubusercontent.com/59199289/206143972-2f568588-c48c-45f3-a930-920018e50ae4.png)

Come possiamo procedere? C'è qualcosa da rivedere nell'installazione o potrebbe essere un bug del Demo SPID?

Grazie mille!

Contributor guide

Open the contributing guide

Research direction

Start with the `spid-compliant-certificates` generator and the `spid-compliant-certificates validator --sector public` entry points, using the command and certificate parameters shown in the report. Compare their result with SPID Validator 1.9.2 and SPID SP Test 1.2.5, focusing on the `SubjectDN must contain name attribute [organizationIdentifier, 2.5.4.97]` discrepancy. Done means the cause of the differing validation results is identified and the expected behavior is clarified or corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.