Consent and statement extensions

[msacrea]

added plan endpoint
added consent endpoint
added contract type of the pension plan
added details about the retirement capital development for the previous year
added total amount available to pledge as collateral for financing home ownership
added standard response 500
general description improvements

[dkoeni]

Please await discussion with ca security for the consent endpoint.

[micmuell]

Please await discussion with ca security for the consent endpoint.

@dkoeni @msacrea in order to have a new stable baseline, I suggest to do this pull to main. However, we can wait with a new version/release until this topic is clarified with ca security (hopefully within the next few days/weeks). @dkoeni if you agree could you unblock the merge? thanks!

[dkoeni]

@micmuell @msacrea Currently, the consent definition of ca-pension is not compatible with the work of ca-security (https://github.com/swissfintechinnovations/ca-security/wiki/Consent-Management). I would not like to include an incompatible version of the consent in the repo, as this would ignore all of ca-security's thoughts on threat models and best practices. If you still want to pursue your approach, I have 3 questions:

• Where does this approach of the consents come from and what makes it more suitable for the ca-pension compared to the approach of ca-security?
• Were established frameworks used in the design of the consents and how can security be guaranteed by the endpoint?
• What is the added value of this consent definition?

Thanks for the input! We agree that the consent management needs to be discussed and solved in an overarching way. Due to urgent demand from the developing partner we commit this changes now to main - but we will hold the release.