EdgeHub: Resync service identity if client request cannot be authenticated #556
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.
Currently, EdgeHub pulls service identities of devices/modules in scope and caches them locally. This cache is re-synced every hour (configurable).
If during this time, the client key was updated in IoTHub, the subsequent authentication will fail for the client if the client tried to connect to EdgeHub. To prevent this, if the authentication of an identity in scope fails locally, try to resync the identity with IoTHub and authenticate again.