Class
HaslContext
unstable since: 1.0
Instance methods
hasl_context_add_mechanism
Registers type in ctx with the given name. name should follow the
convention from
RFC4422ยง3.1.
since: 0.1.0
hasl_context_get_allow_clear_text
Gets whether or not it’s okay to use mechanisms that use clear text with a
non-TLS connection. Clear text methods are ones that use credentials
directly like the PLAIN mechanism which depend on TLS to secure the credentials.
since: 0.1.0
hasl_context_get_authzid
Gets the authzid of ctx. See HaslContext:authzid for more information.
since: 0.1.0
hasl_context_get_current_mechanism
Gets the name of the current mechanism that ctx is attempting.
since: 0.1.0
hasl_context_get_supported_mechanisms
Gets a space separated alphabetically sorted list of all the mechanisms that
ctx knows about.
since: 0.1.0
hasl_context_next
Ask the context to move to the next possible mechanism. The context will create an instance of the mechanism to use internally and return the name that should be given to the server.
since: 0.1.0
hasl_context_set_allow_clear_text
Sets whether or not mechanisms that depend on clear text credentials are
allowed. The PLAIN mechanism is an example of a clear text based mechanism
as it depends on TLS to secure the credentials.
since: 0.1.0
hasl_context_set_allowed_mechanisms
Sets the list of mechanism that are allowed for ctx.
since: 0.1.0
hasl_context_set_authzid
Sets the authzid of ctx to authzid. See HaslContext:authzid
for more information.
since: 0.1.0
hasl_context_step
Calls hasl_mechanism_step() for the currently active mechansim in
ctx.
since: 0.1.0
Properties
Hasl.Context:allow-clear-text
Determines where or not mechanisms that depend on transport layer encryption like TLS are allowed to be used on a non-TLS connection.
unstable since: 1.0
Hasl.Context:allowed-mechanisms
A list of mechanisms that are allowed to be used by this context. This list can be either white space or comma separated.
since: 0.1.0
Hasl.Context:authzid
The identifier for the user who is authenticating. This are times when an administrator wants to authenticate as a user, so they property will be set to the username of the user to authenticate as, but the username and password fields will be proper values for the administrator.
since: 0.1.0
Hasl.Context:tls
Tells the context whether or not the connection is being ran on is over TLS or not.
since: 0.1.0
Hasl.Context:username
The username of the user that is authenticating for mechanisms that need it.
since: 0.1.0
Signals
Signals inherited from GObject (1)
GObject::notify
The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.
unstable since: 2.0