Move authentication of backends back to the client

Since this change the client is responsible to provide credentials
to use to authenticate backends (through ESource-s, to be more precise),
unless the credentials are already saved.
This commit is contained in:
Milan Crha
2015-02-02 14:50:27 +01:00
parent a5fda150c6
commit a6e34f0bb7
66 changed files with 1524 additions and 1055 deletions

View File

@ -35,4 +35,36 @@ If you choose to continue, you may not have access to some of your old data.
<button _label="Keep _Waiting" response="GTK_RESPONSE_CANCEL"/>
</error>
<error id="source-get-values-failed" type="warning">
<_primary>Failed to get values from '{0}'</_primary>
<secondary>{1}</secondary>
</error>
<error id="source-invoke-authenticate-failed" type="warning">
<_primary>Failed to invoke authenticate for '{0}'</_primary>
<secondary>{1}</secondary>
</error>
<error id="source-connection-error" type="error">
<_primary>Failed to connect to '{0}'</_primary>
<secondary>{1}</secondary>
<button _label="_Reconnect" response="GTK_RESPONSE_APPLY"/>
</error>
<error id="source-credentials-prompt-failed" type="warning">
<_primary>Failed to prompt for credentials for '{0}'</_primary>
<secondary>{1}</secondary>
</error>
<error id="source-trust-prompt-failed" type="warning">
<_primary>Failed to finish trust prompt for '{0}'</_primary>
<secondary>{1}</secondary>
</error>
<error id="source-connection-trust-error" type="error">
<_primary>SSL certificate for '{0}' is not trusted.</_primary>
<_secondary>Reason: {1}</_secondary>
<button _label="_View Certificate" response="GTK_RESPONSE_APPLY"/>
</error>
</error-list>