guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jmuehl...@apache.org
Subject [2/4] incubator-guacamole-manual git commit: GUACAMOLE-292: Document new user profile columns of guacamole_user.
Date Wed, 07 Jun 2017 04:05:34 GMT
GUACAMOLE-292: Document new user profile columns of guacamole_user.


Project: http://git-wip-us.apache.org/repos/asf/incubator-guacamole-manual/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-guacamole-manual/commit/9687be91
Tree: http://git-wip-us.apache.org/repos/asf/incubator-guacamole-manual/tree/9687be91
Diff: http://git-wip-us.apache.org/repos/asf/incubator-guacamole-manual/diff/9687be91

Branch: refs/heads/staging/0.9.13-incubating
Commit: 9687be9137e55a062bb5487289a97c36890348fc
Parents: b69d98e
Author: Michael Jumper <mjumper@apache.org>
Authored: Sun Jun 4 15:47:34 2017 -0700
Committer: Michael Jumper <mjumper@apache.org>
Committed: Tue Jun 6 20:43:57 2017 -0700

----------------------------------------------------------------------
 src/chapters/jdbc-auth.xml | 43 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 43 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-guacamole-manual/blob/9687be91/src/chapters/jdbc-auth.xml
----------------------------------------------------------------------
diff --git a/src/chapters/jdbc-auth.xml b/src/chapters/jdbc-auth.xml
index 710a2ff..40fdf12 100644
--- a/src/chapters/jdbc-auth.xml
+++ b/src/chapters/jdbc-auth.xml
@@ -805,6 +805,49 @@ postgresql-user-required: true</programlisting>
                             zones.</para>
                     </listitem>
                 </varlistentry>
+                <varlistentry>
+                    <term><property>full_name</property></term>
+                    <listitem>
+                        <para>The user's full name. Unlike the username, this name
need not be
+                            unique; it is optional and is meant for display purposes only.
Defining
+                            this value has no bearing on user identity, which is dictated
purely by
+                            the username. User accounts with no associated full name should
have
+                            this column set to <constant>NULL</constant>.</para>
+                    </listitem>
+                </varlistentry>
+                <varlistentry>
+                    <term><property>email_address</property></term>
+                    <listitem>
+                        <para>The user's email address, if any. This value is optional,
need not be
+                            unique relative to other defined users, and is meant for display
+                            purposes only. Defining this value has no bearing on user identity,
+                            which is dictated purely by the username. If the user has no
associated
+                            email address, this column should be set to
+                            <constant>NULL</constant>.</para>
+                    </listitem>
+                </varlistentry>
+                <varlistentry>
+                    <term><property>organization</property></term>
+                    <listitem>
+                        <para>The name of the organization, company, etc. that the
user is
+                            affiliated with. This value is optional and is meant for display
+                            purposes only. Defining this value has no bearing on user identity,
+                            which is dictated purely by the username. Users with no associated
+                            organization should have this column set to
+                            <constant>NULL</constant>.</para>
+                    </listitem>
+                </varlistentry>
+                <varlistentry>
+                    <term><property>organizational_role</property></term>
+                    <listitem>
+                        <para>The role or title of the user at the organization described
by the
+                                <property>organization</property> column. This
value is optional and
+                            is used for display purposes only. Defining this value has no
bearing on
+                            user identity, which is dictated purely by the username. Users
with no
+                            associated organization (or specific role/title at that organization)
+                            should have this column set to <constant>NULL</constant>.</para>
+                    </listitem>
+                </varlistentry>
             </variablelist>
             <important>
                 <para>If you choose to manually set unsalted password hashes, please
be sure you


Mime
View raw message