Server: OAuth 2.0 Client list breaks when secret is shown

[MariusBluem]

We could fix this by not showing the secret and instead only provide a "copy secret to clipboard" link.

Version: Master
Browser: Firefox

@nextcloud/designers

[nextcloud-bot]

GitMate.io thinks possibly related issues are https://github.com/nextcloud/server/issues/11056 (OAuth 2.0: ClientNotFoundException), https://github.com/nextcloud/server/issues/3599 (Nextcloud as OAuth 2.0 provider), https://github.com/nextcloud/server/issues/10442 (Contact list broken layout), https://github.com/nextcloud/server/pull/11751 (14.0.2), and https://github.com/nextcloud/server/issues/2595 (Client fails to connect since 10.0.2).

[jancborchardt]

This already is too wide even just with the Client ID and the rest. And it looks like a very bland table.
We should check how others do it – here are examples from Twitter and Github (or is this not a comparable view?):

• with icons
• prominent name
• when it was last used

[rullzer]

Well our OAuth is the other way around. We are the server.
Also we can't show the icons since well we do not know.

Of course we could somehow improve here sure. But not for 16 I guess anymore.

[tcitworld]

We could fix this by not showing the secret and instead only provide a "copy secret to clipboard" link.

Sorry to bump into this right now.

I have seen several users creating a token on their laptop to sign-in into DAVx5 for example, and typing it by hand, because they're not used to open Nextcloud into their mobile browser. Unless there's a better flow to create app tokens on mobile apps, I advise against this.

[rullzer]

@tcitworld this is not the same as the app password settiungs. Oauth is only for the admins