[GUACAMOLE-395] User "expired" column not actually queried for MySQL

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.9.14
• Component/s: guacamole-auth-jdbc-mysql
• Assignee: Mike Jumper
• Reporter: Mike Jumper
• Created: 25/Sep/17 18:38
• Updated: 25/Sep/17 19:01
• Resolved: 25/Sep/17 19:01

Description

Though the expired column of the guacamole_user table is correctly mapped for PostgreSQL:

    <!-- Result mapper for user objects -->
    <resultMap id="UserResultMap" type="org.apache.guacamole.auth.jdbc.user.UserModel" >
        ...
        <result column="disabled"            property="disabled"           jdbcType="BOOLEAN"/>
        <result column="expired"             property="expired"            jdbcType="BOOLEAN"/>
        <result column="access_window_start" property="accessWindowStart"  jdbcType="TIME"/>
        ...
    </resultMap>

it is not mapped at all for MySQL:

    <!-- Result mapper for user objects -->
    <resultMap id="UserResultMap" type="org.apache.guacamole.auth.jdbc.user.UserModel" >
        ...
        <result column="disabled"            property="disabled"           jdbcType="BOOLEAN"/>
        <result column="access_window_start" property="accessWindowStart"  jdbcType="TIME"/>
        ...
    </resultMap>

This column controls manual password expiration, which is thus broken for MySQL and MariaDB databases.

See also: http://guacamole.incubator.apache.org/doc/gug/jdbc-auth.html#jdbc-auth-schema-users