How to get the Sending Server from Notifications without request signature

[KrausMatthias]

Hi,

I'm currently trying to implement the 1.2.0 spec in OpenCloudMesh-rs.

As far as I understand the providerId identifying a share is only unique per provider (Sending Server), so to uniquely identify a share I need providerId and the Sending Server.

If there is a request signature, I could get the Sending Server via the keyId, but as the request signature is optional I don't necessarily have that and I don't see how I would get the Sending Server then, e.g. from a SHARE_UNSHARED notification?

[mickenordin]

You should get the sending server by parsing the sender field, that means splitting the string on @ and taking the last part. For instance if I send you a share, the sender will be: kano@sunet.se@sunet.drive.sunet.se in that case, the sending server is sunet.drive.sunet.se.

[mickenordin]

The process is discribed here: https://github.com/cs3org/OCM-API/blob/develop/IETF-RFC.md#process

And by the way, very cool that you are doing a rust implementation of OCM. You are welcome to join the matrix channel if you haven't already: https://matrix.to/#/#cs3org_OCM:gitter.im if you like to chat or ask questions.

[KrausMatthias]

Thank you! As far as I can tell the sender is only contained in the Share Creation Notification to /shares, but not in the Notifications to /notifications ?

[mickenordin]

Thank you! As far as I can tell the sender is only contained in the Share Creation Notification to /shares, but not in the Notifications to /notifications ?

I see, yes, I think you are right. This looks like a spec bug, we reference Share Creation Notification for providerId, but we don't have sender in other notifications. We should have that.

[glpatcern]

Closing this as the "fix" (use httpsig) was merged. We know we have a broader work to do with notifications, which goes beyond this specific issue.