Update Process Layer/Onboarding

[HeinrichPet]

3_3_1_Onboarding.md

• Update to the state from RuleBook "4.2.1.1 Admission of service providers".
• What informations are needed for the certification process, registration to DAPS and ParIS?
• Availabilty Setup must be updated. DMZ can be used, but also external Cloud services etc. Currently no need to distinction betwenn internal/external connector, cause no implementation supports that.
• Connector Configuration is very dependend on the connector implementation. For onboarding a connector we have to figure out what the minimal common configuration is (x509, URL, TLS certificate, ?).
• Not sure if we need the security setup section in onboarding. We maybe should put the verification in the exchanging data
• Clearify if there will be a process of automatically getting the x509 certificate. Currently it is transfered manually via EMail, Matrix, ...

Consider besides Connector (Data Provider/Consumer) onboarding also:

• Broker
• AppStore,
• Clearing House,
• Vocabulary Provider,
• DAPS,
• ParIS
• Service Provider,
• Data Owner,
• Data User,
• App Provider

[HeinrichPet]

@ssteinbuss Should we copy and maybe detail the IDS onboarding parts from Rule book 4.2.1.1 or should we refer to the rule book?
The same question applies, of course, to many of the processes that are also written up in the Rule Book.

[ssteinbuss]

@HeinrichPet : good point. For me, there should be again a clear distinction between RAM and RuleBook. The RAM should focus on the technical steps and the RuleBook should then indicate and explain the organizational flow. Please take the processes from the RuleBook as foundation and detail here. The Rule Book should then only cover the administrative aspects.

I assume you refer to the onboarding process in section 4.2.1.1.1? There are not too many other processes?

[ssteinbuss]

see also #67

[sebbader]

I have added my view in #76, however not regarding any relations between the RAM and the Rule Book yet.

[ssteinbuss]

Closed by #193