Add UI or CLI Interface to Register the Agent in the Event Protocol Registration Fails

[rwbaskette]

We're using the Drata agent on Debian 12 Bookworm with the KDE Desktop. For one reason or another the deb install package works fine with Gnome but protocol registration fails to work under KDE causing my user not to be able to register their Drata Client. Instead the "auth-drata-agent" URI is opened a browser instance to "site can't be reached" error.

We understand KDE and Debian are not officially supported, but it appears to be trying to be freedesktop compliant.

Thankfully the project is open source and we were able to read the code. To work around this issue, we wrote a script to register the client manually and after restart we had success.

Gist of workaround:
https://gist.github.com/rwbaskette/7474ac6f5e44d50ad2c1ca4c16e104c2

So, in order to skip this potential problem in future, can we get a way to register the client on the CLI for advanced users or a UI option to add the token from the website?

Thank You!

[mnrdrata]

Thank you for letting us know. There are some specific Ubuntu+GNOME default expectations, but it shouldn't affect deep link behavior like this. If there is a specific error on protocol registration available, then it would be helpful to investigate.

There is an option menu accessible by holding alt/opt while brining up the menu that will allow you to manually register the Agent when deep link does not work. That would be the currently supported workaround. Please see

drata-agent/src/renderer/components/Header/SettingsMenu.tsx

Line 199 in 731fdaa

<span>{_t({ id: 'Register' })}</span>

and

drata-agent/src/renderer/components/Header/SettingsMenu.tsx

Line 99 in 731fdaa

setExtraMenu(evt.altKey ?? false);

.

The only concern with alternatives or scripts would be modifying the local storage file while the Agent is running.

[rwbaskette]

Thank you for the workaround, that's much better than my brute force bash script.

What was funny is that it didn't exhibit any error, it just ignored the protocol registration. It was listed in ~/.config/mimeapps.list and when querying with xdg it seemed to ignore it. If we setup a new workstation w/ KDE we'll be more intentional and submit a feature request with better logs. Otherwise, stock Debian 12 + firmware with KDE as the chosen desktop works great in all other aspects and this may be a one-off.

Thank you for making the tool available here and on Linux!