-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for SML certificate update #70
Comments
A generic version is available at https://peppol.helger.com/public/menuitem-tools-smp-sml#tab_updatecert |
Greetings, I am sorry that this question is not directly tied to the SMP software but this seemed like the most appropriate place to put it anyway. I tried https://peppol.helger.com/public/menuitem-tools-smp-sml#tab_updatecert to update our SMP pilot certificate to the newer V3 certificate and get the following error: Error preparing migration of SMP certificate at SML 'https://acc.edelivery.tech.ec.europa.eu/edelivery-sml'. Technical details: ClientTransportException Der Server hat HTTP-Statuscode 401 gesendet: Unauthorized and I cannot get further. I believe this error has something to do with the keystore I provide but I cannot figure out what is wrong. The keystore has one entry containing our old (still valid) certificate (complete chain) and the corresponding private key. I tried with an empty password on the keystore and the entry itself without any luck. Can you please advise how to proceed? Edit: Regards, Emil |
@emilbokenstrand there are multiple things to consider:
I assume you matched all the requirements. Maybe we can have a short Skype session where you can share screen. My Skype ID is phelger |
My bad. I had messed up the new certificate. Sorry for causing any inconvenience, I succeeded in the update now. I made a contact request on Skype btw. Thumbs up for this fix, nice to have it available directly in the SMP. |
UPDATING THE SML WITH A NEW SMP CERTIFICATE:
PrepareChangeCertificate operation
SMP with expired certificate
PEPPOL_Certificates_Change_V1.2.pdf
The text was updated successfully, but these errors were encountered: