I agree. All the infrastructure for sending a message is available, we only have to decide how to handle the translations. Should we offer some pre-defined messages in the client or should the messages be generated on the server side? I would prefer the latter one.

I agree that the messages should be generated server-side.

We should probably have predefined messages client side.
Otherwise we'd need to pass down to the server the client language and locale and play tricks to generate the message in the right language.

The message template (the actual wording) should probably be defined on the client side and support multiple languages. The arguments to the message (if any) should be defined on the server and inserted into the message template on client on the fly at the moment when message template is turned into a message.

Fields changed

milestone: SSSD Deferred => SSSD 1.1

Fixed by: 5136873b1fd56e34172e5fb325ac2b5508c85f31

doc: 0 => 1
fixedin: => 1.1.0
resolution: => fixed
status: new => closed
tests: 0 => 1

The documentation should mention that a message is display if the cached credentials are used for authentication, i.e if the system is offline. The message might also indicate how long the cached credential is valid, i.e how log offline authentication is possible.

Fields changed

rhbz: => 0

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1281

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.