ask for a password synchronously. If the implementation returns gio.types.TlsInteractionResult.Handled, then the password argument should have been filled in by using gio.tls_password.TlsPassword.setValue or a similar function.
ask for a password asynchronously.
complete operation to ask for a password asynchronously. If the implementation returns gio.types.TlsInteractionResult.Handled, then the password argument of the async method should have been filled in by using gio.tls_password.TlsPassword.setValue or a similar function.
ask for a certificate synchronously. If the implementation returns gio.types.TlsInteractionResult.Handled, then the connection argument should have been filled in by using gio.tls_connection.TlsConnection.setCertificate.
ask for a certificate asynchronously.
complete operation to ask for a certificate asynchronously. If the implementation returns gio.types.TlsInteractionResult.Handled, then the connection argument of the async method should have been filled in by using gio.tls_connection.TlsConnection.setCertificate.
The class for #GTlsInteraction. Derived classes implement the various virtual interaction methods to handle TLS interactions.
Derived classes can choose to implement whichever interactions methods they'd like to support by overriding those virtual methods in their class initialization function. If a derived class implements an async method, it must also implement the corresponding finish method.
The synchronous interaction methods should implement to display modal dialogs, and the asynchronous methods to display modeless dialogs.
If the user cancels an interaction, then the result should be gio.types.TlsInteractionResult.Failed and the error should be set with a domain of G_IO_ERROR and code of gio.types.IOErrorEnum.Cancelled.