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
Continue consolidating the auth methods for the hub device #2854
Conversation
…okenRefresh, rename ClientAuthenticationWithToken to ClientAuthenticationWithSharedAccessSignature
iothub/device/src/Authentication/AuthenticationWithTokenRefresh.cs
Outdated
Show resolved
Hide resolved
I'd like to hold this for now until we have the v2 sync meeting to decide if anything else we want to consolidate further for the auth methods in the hub device. |
iothub/device/src/Authentication/Security/SharedAccessSignatureBuilder.cs
Outdated
Show resolved
Hide resolved
iothub/device/src/Authentication/AuthenticationWithTokenRefresh.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the changes that you have here. We'll still want to discuss if we need both ClientAuthenticationWithRegistrySymmetricKey and ClientAuthneticationWithSakRefresh.
…nRefresh, and update unit tests
…cationWithRegistrySymmetricKey and ClientAuthenticationWithSharedAccessPolicy
…ogging for large value of TTL and renewal buffer
iothub/device/src/Authentication/ClientAuthenticationWithSakRefresh.cs
Outdated
Show resolved
Hide resolved
iothub/device/src/Authentication/IotHubConnectionCredentials.cs
Outdated
Show resolved
Hide resolved
iothub/device/src/Authentication/ClientAuthenticationWithSakRefresh.cs
Outdated
Show resolved
Hide resolved
iothub/device/src/Authentication/ClientAuthenticationWithSakRefresh.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs a migration guide update
iothub/device/src/Authentication/ClientAuthenticationWithSakRefresh.cs
Outdated
Show resolved
Hide resolved
…SharedAccessKeyRefresh
iothub/device/src/Authentication/ClientAuthenticationWithSharedAccessKeyRefresh.cs
Show resolved
Hide resolved
iothub/device/src/Authentication/ClientAuthenticationWithTokenRefresh.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of small comments
…sh and fix ordering of param
…fix ordering of param
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
What's addressed in this PR:
ClientAuthenticationWithConnectionString.cs
,ClientAuthenticationWithRegistrySymmetricKey.cs
andClientAuthenticationWithSharedAccessPolicy.cs
intoClientAuthenticationWithSakRefresh.cs
After these changes, the auth methods on the hub device side will be like this.