Signing API based on JWS#527
Merged
sebbader-sap merged 16 commits intoIDTA-01002-3-2_workingfrom Mar 29, 2026
Merged
Conversation
Idta 01002 3 2 working
Contributor
Author
|
Might dublicate #523 ... |
|
Yes, this is a duplicate of #523 Probably created accidentally |
|
Close because duplicate |
* Add V3.1.2 Bugfixes into V3.2.0 (#541) * fix ServiceSpecificationProfileEnum values for 3.0 and 3.1 * remove TREE (#539) * remove v3.2 profile uris --------- Co-authored-by: Martin Stemmer <52048213+Martin187187@users.noreply.github.com> * remove GetAllAssetAdministrationShellDescriptorsByAssetType from openapi (#530) * added changelog for new signing operations and profiles * undo changes to the profiles table * fix typo --------- Co-authored-by: sebbader-sap <107036549+sebbader-sap@users.noreply.github.com> Co-authored-by: Martin Stemmer <52048213+Martin187187@users.noreply.github.com>
Contributor
Author
sebbader-sap
requested review from
BirgitBoss,
alexgordtop,
aorzelskiGH,
danielporta,
g1zzm0,
mjacoby,
waltersve and
zrgt
as code owners
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
...ation/IDTA-01002-3/modules/ROOT/pages/http-rest-api/service-specifications-and-profiles.adoc
Fixed
Show fixed
Hide fixed
ConceptDescriptionRepositoryServiceSpecification/V3.2_SSP-003.yaml
Dismissed
Show dismissed
Hide dismissed
sebbader-sap
commented
Mar 29, 2026
Contributor
Author
|
merging this one as #523 misses the OpenAPI files |
| Some use cases of the Asset Administration Shell require the proof that data has not been changed and that it is still the original data of the AAS originator. | ||
| An example is a device manufacturer supplying to an integrator supplying to a plant operator. The plant operator wants to check the remained integrity of the device manufacturer's AAS. | ||
|
|
||
| The AASX package format includes the possibility of signing an AASX package, but this is rarely used. AASX packages can also not be protected by AAS security and access rules. This is why signatures are needed as part of the API. |
Check warning
Code scanning / QDJVMC
Typo Warning documentation
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #521