What is needed from the nemlogin to configure the signature server?

[lilosti]

We have derived from the installation process that we need:

entity-id: [your saml metadata url from the nemlogin admin setup]
keystore-class-path: [your nemlogin p12 filename - uses the same folder as this settings file]
key-pair-alias: ["The name of your certificate"]
keystore-password: [cert password]
private-key-password: [cert password]

And maybe we also need som kind of certificate. It would be very nice if this information was available in the configuration part of the readme, and also information on where the certifcate should be stored.

[lilosti]

@ds-bellcom @skifter please help!

[skifter]

@lilosti If this helps i will add it to the README. cc @ds-bellcom

Certificate:
The certificate is an OCES cert. generated like when you use e.g. Digiatal Post (via MitID erhverv). The public part / pem file has to be uploaded to the nemlogin admin for the server
To generate a cert go to: https://erhvervsadministration.nemlog-in.dk/certificates

You get a p12 file that needs to be added to the configuration file with a path relative to that file. If the p12 file is in the same folder as the config file it would be like below.

Where to store the certificate:
The config file is in examples/nemlogin-signing-webapp/src/main/resources/
If the cert file is in the same folder the path in the config file is
"keystore-class-path: /Certificate_for_Signing_purpose.p12"

key-pair-alias: ["The HUMAN READABLE name of your certificate"]
e.g. key-pair-alias: "certificate for signing purpose"
keystore-password: Your p12 certificate password
private-key-password:Your p12 certificate password.

Nemlogin metadata url:
entity-id: [your saml metadata url from the nemlogin admin setup]
E.g. entity-id: https://saml.sign.nemlogin3.bellcom.dk - it is defined in the nemlogin admin setup for your service

[ds-bellcom]

@lilosti, please remember to tag Jørn and me when you create issues that we need to address. Otherwise, we risk time passing like with this issue, where we don't see the issue and only become aware of it when you tag us.

Thanks in advance.

[lilosti]

@ds-bellcom @skifter I will try to remember to tag you. I think your addition to the readme would be very nice @skifter , thank you!

[lilosti]

@skifter @ds-bellcom please update the reamde

[lilosti]

and and.. where does the metadata file needed here, come from:

[lilosti]

@ds-bellcom @skifter

[gBarlach]

@ds-bellcom I expect this to be free of carge as part of delivery of Digital Server. Please tag Anna-Lis and I in any issues with ecconomic impact on OS2forms.

[skifter]

@gBarlach @lilosti @ds-bellcom

It is not part of the delivery. The documentation that is now requested is about setting up a "normal" IT system in Nem-login integration. It is a third-party system. The only change for Digital Signature you need to make is to check a checkbox in your normal nemlogin setup.

Here are the best links for documentation:

• Metadata: https://tu.nemlog-in.dk/oprettelse-og-administration-af-it-systemer/metadata/
• Test metadata: https://test-nemlog-in.dk/Testportal/Test-nemlog-in-2.xml
• Nemlogin setup: https://cms.nemlog-in.dk/media/uz0ab3gi/18-integration-with-nemlog-in-local-idp-v1-2.pdf
• Validator: https://metadatavalidator.test-devtest4-nemlog-in.dk/

[ds-bellcom]

@skifter @ds-bellcom please update the reamde

@lilosti the readme is updated here: https://github.com/MitID-Digital-Signature/Signing-Server/blob/develop/README.md