feat(endpoint): add support for transferPath and replace token key to authorization with bearer - #23
Conversation
… authorization with bearer
| @@ -0,0 +1,71 @@ | |||
| /* | |||
| * Copyright 2025 Seamless Middleware Technologies S.L and/or its affiliates | |||
There was a problem hiding this comment.
I think this one is the correct now (https://github.com/SEAMWARE/fdsc-edc/blob/main/license-header.txt). The other one seems to be a legacy one, used in the past maybe with license-maven-plugin or something like that
| FDSCDataAddress.Builder.newInstance() | ||
| .clientId(dataFlow.getId()) | ||
| .property(EDC_NAMESPACE + "token", signedJWT.serialize()) | ||
| .property(EDC_NAMESPACE + "authorization", "Bearer " + signedJWT.serialize()) |
There was a problem hiding this comment.
is the bearer prefix expected by the frontend? I checked the spec and they define the optional "authType" property, that contains the info of it being a bearer token: https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1-err1/#transfer-start-message
There was a problem hiding this comment.
In our current implementation, I saw that under tokenType
{
"@type": "DataAddress",
"tokenType": "bearer",
...
}
I'll change it and try again with the UI
There was a problem hiding this comment.
Yes, in our implementation it was wrong in any way...
…rding to DSP standard
3 participants
No description provided.