Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Is it possible to set ClientId from server?
See original GitHub issueIf I’m sending a message from inside of the server via MQTTServer.PublishAsync , is it possible to set a client id somehow? In other words, I’d like to impersonate a particular client from within the server.
TIA!
Issue Analytics
- State:
- Created 4 years ago
- Comments:9
Top Results From Across the Web
Is it possible to set ClientId from server? · Issue #660
If I'm sending a message from inside of the server via MQTTServer.PublishAsync , is it possible to set a client id somehow?
Read more >Google Sign-In for server-side apps | Authentication
Step 1: Create a client ID and client secret · Go to the Google API Console. · From the project drop-down, select an...
Read more >The Client ID and Secret - OAuth 2.0 Simplified
The client_id is a public identifier for apps. Even though it's public, it's best that it isn't guessable by third parties, so many ......
Read more >Control.ClientID Property (System.Web.UI)
The ClientID value is set to the value of the ID property. If the control is a naming container, the control is used...
Read more >How does the Linux NFS server implementation of ...
I have been trying to create an identical server, but I just don't seem to be able to. I configured everything on the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
When using MQTTv5 you can leave the client id empty and the server will generate/choose one and returns it in the PUBACK packet. This is also supported in this library.
I am just referring to the server. There you can already intercept entire messages and publish custom messages. So setting the ClientId (instead of using the servers default one) should be fine in my opinion.
But you are right with security concerns. But the users is responsible for this if he really want to use a custom client ID for some (strange) Use Case. I would rather not do that but I accept that this might a Use Case for someone else. What do you think?