BUG : upload_certificate Endpoint Missing verifications. #2501

Activity

1. rachik-hue

   self-assigned this

   on Sep 1, 2026
2. rachik-hue

   added

   security

   on Sep 1, 2026
3. rachik-hue

   added the

   Task

   issue type on Sep 1, 2026
4. rachik-hue

   updated Priority High on Sep 1, 2026
5. rachik-hue

   changed the issue type from

   Task

   to

   Bug

   on Sep 1, 2026
6. rachik-hue

   set

   Severity

   to

   MAJOR

   on Sep 1, 2026
7. rachik-hue

   added this to the eSignet_v2.0.1 milestone on Sep 1, 2026
8. rachik-hue

   added a related issue on Sep 1, 2026

   • eSignet - Thunder: Security testing For the eSignet Go version #2335
9. rachik-hue

   assigned

   Md-Humair-KK

   and unassigned

   rachik-hue

   on Sep 28, 2026
10. rachik-hue

    set

    Complexity

    to

    MEDIUM

    on Sep 28, 2026
11. Md-Humair-KK commented on Oct 5, 2026

    

    Md-Humair-KK

    on Oct 5, 2026

    Collaborator

    More actions

    PR raised - #2659
12. zesu22

    linked a pull request that will close this issue2501 BUG : upload_certificate Endpoint Missing verifications. #2659on Oct 14, 2026
13. anushasunkada commented on Oct 14, 2026

    

    anushasunkada

    on Oct 14, 2026

    Contributor

    More actions

    @Mahesh-Binayak, this is an invalid bug. A CSR is required to obtain a new certificate signed by a different CA (either self-signed or another authority). It’s still acceptable to get an eSignet certificate signed by a different CA rather than an internally created hierarchy. Ultimately, the same certificate should be submitted to IDA to re-onboard. Therefore, the PMS should also trust this certificate before partner onboarding.

    cc: @rachik-hue @Md-Humair-KK
14. rachik-hue

    assigned

    Mahesh-Binayak

    and unassigned

    Md-Humair-KK

    on Oct 15, 2026
15. rachik-hue

    modified the milestones: eSignet_v2.0.1, eSignet_v2.1.0 on Oct 15, 2026