Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Authorization management is necessary because all clients/systems operating within a given SLA may not be allowed to have equal access to data

User and role modelling

Authorization is managed on the SLA level. Each connecting system/client may be assigned an identity (a user) having a number of roles, corresponding to the different operations in the bit repository. Each identity/user is assigned a certificate, which may be revoked in case it is compromised. Message xml bodies are signed or encrypted using a user/identitys certificate, ensuring authenticity

  • No labels