Skip to content
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

Investigate eIDEasy suitability #599

Closed
loorm opened this issue Dec 7, 2020 · 5 comments
Closed

Investigate eIDEasy suitability #599

loorm opened this issue Dec 7, 2020 · 5 comments
Labels
investigate Need to find out more about this.

Comments

@loorm
Copy link
Member

loorm commented Dec 7, 2020

There is a service - https://eideasy.com/ - that might be useful for us. Need to look into it a bit.

@loorm loorm added the enhancement Making an existing feature better. label Dec 7, 2020
@loorm loorm added this to Ready for prioritization (triage) in Citizen OS GitHub issue priorities via automation Dec 7, 2020
@loorm loorm added investigate Need to find out more about this. and removed enhancement Making an existing feature better. labels Dec 15, 2020
@loorm
Copy link
Member Author

loorm commented Dec 15, 2020

Triage 31. Yes, let's look into it, but priority is lowish.

@loorm loorm moved this from Ready for prioritization (triage) to TODO - prioritized for development in Citizen OS GitHub issue priorities Dec 15, 2020
@ilmartyrk
Copy link
Member

ilmartyrk commented Mar 12, 2021

Pros:

  • Supports multiple countries and authentication methods
  • Should be quite easy to setup, API documentation
  • we don't have to maintain our own authentication systems
    Cons:
  • Possibility that we would want to add authentication methods that they don't provide
  • If they have downtime users can't login/sign documents
  • Possibly cost, but this should be calculated https://eideasy.com/pricing/ seems that price is calculated per request
  • Seems that their own js library is not ready yet https://github.com/eideasy/eideasy-js-sdk

Overall, seems like a good alternative if we decide to alter our authentication/signing methods. It also should be easy to implement after reading some API documentation

@ilmartyrk ilmartyrk moved this from TODO - prioritized for development to Ready for prioritization (triage) in Citizen OS GitHub issue priorities Mar 12, 2021
@loorm loorm self-assigned this Mar 17, 2021
@loorm loorm moved this from Ready for prioritization (triage) to In preparation in Citizen OS GitHub issue priorities Mar 17, 2021
@loorm
Copy link
Member Author

loorm commented Mar 17, 2021

Triage 35. Need to do some price calculation and risk analysis.

@loorm
Copy link
Member Author

loorm commented Sep 6, 2021

Financially, this would make sense. We currently pay around 133 euros to Sertifitseerimiskeskus for an average month of 279 signatures (mostly mobile ID). Using eIDEasy, the bill would be around 65 euros.

In terms of risk, though, being dependant on someone for our core functionality does not rate well.

I propose this solution. We keep our own libraries and pay to SK for Estonian eIDs. However, we will remember eIDEasy and if we want to add aditional electronic signatures, we can decide whether to create our own native support or use their API.

WDYT @ilmartyrk?

@ilmartyrk
Copy link
Member

Move to citizenos/citizenos-fe#55

Citizen OS GitHub issue priorities automation moved this from In preparation to Done - live Mar 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigate Need to find out more about this.
Projects
No open projects
Development

No branches or pull requests

2 participants