Attestation/Principal Manager Decoupling
The principal manager is current using the attestation manager to save the userdatas for auto issuing. The attestation manager is later on creating the credetnial with this information by "OfferCredential". This mixes the functionality betweet principal manager and attestation manager. The atttestation manager shall only receive auto issuing requests for arbitary credential types, which are passed then for precise mapping to the related managers. E.g. AUTOISSUE + credentialType=MyCredential is coming in by connection acceptance, then the attestation manager accepts this (by nats) and sends out an request for data mapping to any responsable service. The responsible services register beforehand a credentialType that they can process/fullfill. In the end the attestation manager is just doing issuing, issing pre/post checks and brokering the credential data requests. So there is then no need more for save user infos, or processing "principal" data in attestation manager, which is a architectural lack of seperation of concerns.