Create Ruuter-based SiGa Service Template

[SigritSiht]

AS A {Administrative User / Service Manager / ???} I WANT TO create template for SiGa SO THAT SiGa could be used to create services

Acceptance Criteria

• [x] Set up SiGa locally for development and mock services
• [ ] Use ID-card, Mobile ID, Smart ID and EU eID (the latter if possible)
• [ ] Template can be used for creating service flows buerokratt/Service-Module#20
• [ ] SiGa can be integrated with actual SiGa production
• [ ] Replace SIGA template mock data with live data
• [ ] personIdentifier comes from User Info Cookie Generated by TARA
• [ ] End-User must be authenticated using TARA before using SIGA to be able to provide the end-user country and Phone Number
• [ ] buerokratt/NoOps#109

GUI

• [x] SiGa drag-and-drop element created in buerokratt/Service-Module#6 view

DSL

• [ ] Ruuter DSL-based SiGa Service template (see example) created

Endpoints

• [ ] Use {{ruuter_url}}/jwt/userinfo as an endpoint to get End Client's current session information

This endpoint may contain either mock or actual TIM's response, depending on the environment (play / test vs prod accordingly)

[turnerrainer]

https://www.id.ee/en/article/signing-service-and-digidocservice/ https://github.com/open-eid/SiGa https://open-eid.github.io/allkirjastamisteenus/

[SigritSiht]

Figma link.

[Minwasko]

@turnerrainer currently SiGa template expects an input if you want to sign the document using smartID or mobileID, where does this information come from? It is missing from the design

I don't know if it could come from TARA, but currently it is missing from the TIM mock data as well.

[1AhmedYasser]

@turnerrainer @allarlaaneleht

Regarding Further developments as discussed with Mr.Rainer

1. Some Siga information comes from TARA and some information needs to be asked from the bot side
2. The Siga Template card UI will be changed to give the service administrator the ability to choose the sign type for siga and based on that on the bot side it will ask the user to authenticate using tara based on the requested type in the service siga template
3. In case the user login tara type and the siga template type are the same then the bot will drive the information needed from the cookie and only ask the user for any additional information as country or phone number (Bot Should Check for this)
4. Modify the SIGA template to add ID Cards and add its base url to constants.ini

[1AhmedYasser]

Will Require future developments to modify the Template to add the correct ruuter file uplaoding

Waiting: Ruuter Upload Ability

[turnerrainer]

Blocked by https://github.com/buerokratt/NoOps/issues/109

[ValterAro]

Given that people need PIN 2 to sign a document then they might not prefer the same choice that they used when they did the authentication nor should the choice be made by the service creator. Therefore the choice between ID-card, Mobile ID and Smart ID should be made by the user. I put the current progress "to groom".