Deployment of Suomi.fi e-Authorizations

Familiarise yourself with the Suomi.fi e-Authorizations material and plan use cases for acting on behalf of another party and deployment of the interface service.

Your service can only use Suomi.fi e-Authorizations if you have enabled strong identification. You can enable Suomi.fi e-Identification or a similar identification option.

Start the deployment of the Suomi.fi e-Authorizations by sending an application on the Suomi.fi Service Management websiteOpens in a new window.

If you are a new Suomi.fi Service Management user, register the details of your organisation. If your organisation already has a Service Management customer account, ask a representative of your organisation to send you an invitation to Service Management. You will be automatically added to your organisation’s account. You can then log into Service Management.

Plan a detailed schedule and other details for your deployment in cooperation with the Digital and Population Data Services Agency. Study the following materials carefully:

• Technical material for Suomi.fi e-AuthorizationsOpens in a new window..
• Selection of connection method and interfacesOpens in a new window..

Select the connection method that you intend to use:

• Security server interface (Suomi.fi Data Exchange Layer) (for acting on behalf of a company)
• Web APIOpens in a new window. (for acting on behalf of a person and a company).

Also plan the configuration of the rule engine (management user interface) (person and/or company):

• Rule engine for acting on behalf of another person (Delegate, Authorization)Opens in a new window.
• Rule engine for acting on behalf of a company (Organizational Roles)Opens in a new window.

OPTIONAL:

Select the mandate themes that will be used in your service. You can

• select one or more of the existing mandate themesOpens in a new window., or
• specify new mandate themes.

Familiarise yourself with the instructions for defining mandate themesOpens in a new window..

• If you are using the security server interface, first join the Data Exchange Layer. Opens in a new window.Then install the test security server. Provide the Digital and Population Data Services Agency with the necessary informationOpens in a new window.: Member Class, Member Code and Subsystem Code. The Digital and Population Data Services Agency will establish a test service for your organisation and provide the data you need to join the service.
• If you use Web API, the Digital and Population Data Services Agency will establish a test service for your organisation on the basis of your application and provide the data you need to join the service. Notify the Digital and Population Data Services Agency of the return address.Opens in a new window.

Use the test data provided by the Digital and Population Data Services Agency for testing. Report to the Digital and Population Data Services Agency on the progress of the tests as well as any errors and problems. Make the necessary changes for production.

Information required by the deployment team:

• Extract from the transaction log. The log must show who is acting, on whose behalf, on what matter and when. Read more about the logging requirements.Opens in a new window.
• Screenshots of the service path for acting on behalf of another party.
• Customer guidance.Opens in a new window.

When the development work and testing have been completed, notify the Digital and Population Data Services Agency of the service start date.Opens in a new window.

1. If you are using the security server interface, install the production security server. Notify the Digital and Population Data Services Agency of your Member Class, Member Code and Subsystem Code.
2. If you use Web API, notify the Digital and Population Data Services Agency of the return address.

Notify the Digital and Population Data Services Agency of the name and personal identity code of your organisation’s contact person so that they can be granted access rights to the service rule engine (management user interface).

Configure the rules for the rule engine in the manner planned by your organisation.

Test the functioning of your production environment with authentic data. Train your organisation’s personnel to ensure that they are familiar with new operating models.

Keep the mandate instructions up to date and update the rule engine if changes are made to the service.