OAuthSwift VS CocoaMQTT

Edit: they did say it works with discord in a question someone asked here https://github.com/OAuthSwift/OAuthSwift/issues/597

https://www.raywenderlich.com/243-oauth-2-0-with-swift-tutorial and subsequently OAuthSwift Im still pretty lost on all of this. Do I really need to use a proxy if I can save the app token to the keychain?

Also, there are already OAuth frameworks available, like OAuthSwift. Use what's out there instead of reinventing the wheel, unless absolutely necessary.

I would recommend reading the docs (and maybe source) of https://github.com/OAuthSwift/OAuthSwift and reading the docs on Google’s OAuth implementation. Avoid the ones they have that depend on using their SDK, but look for the web ones instead.

EMQ is also actively promoting the standardization of MQTT over QUIC. We are preparing a draft proposal about MQTT over QUIC after becoming the only Chinese company with voting rights in the OASIS MQTT Technical Committee in 2018 and participating in the 5.0 protocol standard development. We believed that in the near future, the underlying protocol of MQTT will support both TCP and QUIC, benefiting the entire IoT industry.

Internet of Vehicles（IoV）is a typical application of IoT technology in the field of transportation systems. To some extent, the integration layout and collaborative development of relevant technical fields involved in the IoV industry are connected with the IoT. As an open source IoT data infrastructure software supplier, EMQ has provided IoT infrastructure software with cloud-edge collaboration for many customers in the field of IoV for many years. Thus realizing the unified connection of people, vehicles, roads and clouds, and creating intelligent networking, autonomous driving and V2X scenario solutions for vehicle manufacturers, T1 suppliers, aftermarket service providers, travel service companies, etc.

EMQ also realizes LwM2M access capability on the EMQX server and most functions of the LwM2M Protocol. LwM2M device can register to EMQX-LWM2M to access and manage equipment through EMQX-LWM2M. Device can also report information to EMQX-LWM2M and collect data by using EMQ back-end service.

If this is a requirement i would strongly suggest you to use a selfhosted EMQ X broker (https://www.emqx.io/) with a database. Postgresql would be perfect for this. Then you could setup a webpage with an API that can alter the database from which EMQ X is reading the user/password and also the ACL.