Skip to content
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

Add SeAsSecurityMessage interface and unit tests #633

Merged
merged 5 commits into from
Sep 24, 2019

Conversation

kfbehar
Copy link
Contributor

@kfbehar kfbehar commented Sep 23, 2019

Checklist

Reference/Link to the issue solved with this PR (if any)

Description of the problem

Description of the solution

@anthonyvercolano
Copy link
Contributor

anthonyvercolano commented Sep 23, 2019

/azp run node-canary
#Closed

@azure-pipelines
Copy link

azure-pipelines bot commented Sep 23, 2019

Azure Pipelines successfully started running 1 pipeline(s).

#Closed

@kfbehar
Copy link
Contributor Author

kfbehar commented Sep 23, 2019

/azp run node-canary #Closed

@azure-pipelines
Copy link

azure-pipelines bot commented Sep 23, 2019

Commenter does not have sufficient privileges for PR 633 in repo Azure/azure-iot-sdk-node

#Closed

@anthonyvercolano
Copy link
Contributor

anthonyvercolano commented Sep 23, 2019

/azp run node-canary
#Closed

@azure-pipelines
Copy link

azure-pipelines bot commented Sep 23, 2019

Azure Pipelines successfully started running 1 pipeline(s).

#Closed

@kfbehar
Copy link
Contributor Author

kfbehar commented Sep 23, 2019

/azp run node-canary #Closed

@azure-pipelines
Copy link

azure-pipelines bot commented Sep 23, 2019

Azure Pipelines successfully started running 1 pipeline(s).

#Closed

@anthonyvercolano
Copy link
Contributor

anthonyvercolano commented Sep 23, 2019

/azp run horton-node-gate
#Closed

@@ -916,7 +916,7 @@ export class Mqtt extends EventEmitter implements DeviceTransport {
if (message.contentType) systemProperties['$.ct'] = <string>message.contentType;
/*Codes_SRS_NODE_DEVICE_MQTT_16_083: [The `sendEvent` method shall serialize the `contentEncoding` property of the message as a key-value pair on the topic with the key `$.ce`.]*/
if (message.contentEncoding) systemProperties['$.ce'] = <string>message.contentEncoding;

if (message.interfaceId) systemProperties['$.ifid'] = message.interfaceId;
Copy link
Contributor

@anthonyvercolano anthonyvercolano Sep 23, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

['$.ifid'] [](start = 45, length = 10)

Does this clash with digitaltwins? #ByDesign

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a property sent in digitaltwins registration (which uses the telemetry path) that uses this as a property name.


In reply to: 327269387 [](ancestors = 327269387)

Copy link
Contributor Author

@kfbehar kfbehar Sep 23, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was not aware of that, but we are already using that property in other SDKs, so I think it should be fine.
I think it should only be a problem if they use the same property AND the same value, only then is the message routed as a security message. #ByDesign

Copy link
Contributor

@anthonyvercolano anthonyvercolano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@azure-pipelines
Copy link

azure-pipelines bot commented Sep 24, 2019

No pipelines are associated with this pull request.

#Closed

4 similar comments
@azure-pipelines
Copy link

azure-pipelines bot commented Sep 24, 2019

No pipelines are associated with this pull request.

#Closed

@azure-pipelines
Copy link

azure-pipelines bot commented Sep 24, 2019

No pipelines are associated with this pull request.

#Closed

@azure-pipelines
Copy link

azure-pipelines bot commented Sep 24, 2019

No pipelines are associated with this pull request.

#Closed

@azure-pipelines
Copy link

azure-pipelines bot commented Sep 24, 2019

No pipelines are associated with this pull request.

#Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants