| commit | 42203a3d009c2f0651985033506b23f88dad50b3 | |
| author | Milan Crha <mcrha@redhat.com> | |
| Tue, 23 Jan 2018 12:54:45 +0000 (23 13:54 +0100) | ||
| committer | Milan Crha <mcrha@redhat.com> | |
| Tue, 23 Jan 2018 12:54:45 +0000 (23 13:54 +0100) | ||
| tree | fd998c4ad8d81561ef6a52874bef3b17e5202a71 | treesnapshot (tar.gz zip) |
| parent | c1a673bdc27c2975b3c954f1e3424ba4b9809f05 | commitdiff |
Change how UI deals with XOAUTH2 for Camel providers
As it had been before this change, once any account had Google built-in
OAuth2 authentication, it had been offered to every account of that provider,
which is wrong. This change adds/removes particular built-in OAuth2
authentication methods on demand, also when changing server host name,
without influencing any other account.
As it had been before this change, once any account had Google built-in
OAuth2 authentication, it had been offered to every account of that provider,
which is wrong. This change adds/removes particular built-in OAuth2
authentication methods on demand, also when changing server host name,
without influencing any other account.