-
Notifications
You must be signed in to change notification settings - Fork 2
Add signing references to API spec #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: IDTA-01004-3-1_Working
Are you sure you want to change the base?
Add signing references to API spec #50
Conversation
|
|
||
| This document specifies the security for the Asset Administration Shell and its submodels, i.e. how to use Access Tokens and how to define Access Rules for Authorization. | ||
| The signing of submodel data will be specified in a next version of this document. | ||
| Identifiables (i.e. Asset Adminstration Shells, Submodels and Concept descriptions) can also be signed by the additional endpoint /$sign, as described in the REST API specification. |
Check warning
Code scanning / QDJVMC
Typo Warning documentation
|
|
||
| This document specifies the security for the Asset Administration Shell and its submodels, i.e. how to use Access Tokens and how to define Access Rules for Authorization. | ||
| The signing of submodel data will be specified in a next version of this document. | ||
| Identifiables (i.e. Asset Adminstration Shells, Submodels and Concept descriptions) can also be signed by the additional endpoint /$sign, as described in the REST API specification. |
Check warning
Code scanning / QDJVMC
Typo Warning documentation
| A next version of this document shall define signatures (and possibly encryption) of AAS data. | ||
| So far this is only possible together with AASX packages, but signatures are also needed when using APIs to exchange data. | ||
| Some business partners like to copy AAS data to their servers, so that the signature of the originator of the AAS data must be able to be proven by a final receiver. | ||
| Signing of Identifiables is defined in the REST API specification. This may be extended to SubmodelElements or other parts of Identifiables. Currently plain JWS (JSON Web Signature) is used for signing, which may be extended to additional formats e.g. JAdES (JSON Advanced Digital Signature). |
Check warning
Code scanning / QDJVMC
Typo Warning documentation
No description provided.