-
Notifications
You must be signed in to change notification settings - Fork 73
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
[Feature request] Access Iot Hub data with the appropriate RBAC role instead of the Connection String #446
Comments
@TechWatching Thanks for the feedback, this feature is actually in our backlog and will be implemented soon. |
Authentication through AAD has been released in this version: https://github.com/Azure/azure-iot-explorer/releases/tag/v0.15.0 |
@YingXue I have noticed a few problems :
I succeeded to connect to an iot hub with a test account I created on my tenant but I think the problems I mentioned above should be corrected. |
I just installed latest, and when I log in I get no subscriptions even though I have access to multiple IoT hubs. Is there a specific permission one needs to have for this to work? I plan on having someone with more permissions try this out to see if it works. I agree with @TechWatching that it's not possible to change login info. |
Is your feature request related to a problem? Please describe.
I cannot explore an IoT Hub (devices, twin, queries ...) without having the secret connection string of the IoT Hub. For security reasons this connection string is not something always available.
Describe the solution you'd like
I would like to be able to login to Iot hub Explorer with my azure account (supposing that my account already has the appropriate role) and access the IoT hubs my account has permission to explore without having to provide a connection string. This is what I am used to do with the azure storage explorer which is quite similar to the iot hub explorer tool.
Describe alternatives you've considered
I considrered using vs code extension for iot hub, but there is the same issue.
The text was updated successfully, but these errors were encountered: