Github user mike-jumper commented on a diff in the pull request:
https://github.com/apache/incubator-guacamole-manual/pull/34#discussion_r117657021
--- Diff: src/chapters/cas-auth.xml ---
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<chapter xml:id="cas-auth" xmlns="http://docbook.org/ns/docbook";
version="5.0" xml:lang="en"
+ xmlns:xi="http://www.w3.org/2001/XInclude";
xmlns:xlink="http://www.w3.org/1999/xlink";>
+ <title>CAS Authentication</title>
+ <indexterm>
+ <primary>CAS Authentication</primary>
+ </indexterm>
+ <para>CAS is an open-source Single Sign On (SSO) provider that allows
multiple applications
+ and services to authenticate against it and brokes those
authentication requests to a
+ back-end authentication provider. This module allows Guacamole to
redirect to CAS for
+ authentication and user services. This module must be layered on
top of other authentication
+ extensions that provide connection information, as it only
provides user authentication.
+ </para>
+ <section xml:id="cas-downloading">
+ <title>Downloading the CAS authentication extension</title>
+ <para>The CAS authentication extension is available separately
from the main
+ <filename>guacamole.war</filename>. The link for this and
all other
+ officially-supported and compatible extensions for a
particular version of Guacamole are
+ provided on the release notes for that version. You can find
the release notes for
+ current versions of Guacamole here: <link
+
xlink:href="http://guacamole.incubator.apache.org/releases/";
+
>http://guacamole.incubator.apache.org/releases/</link>.</para>
+ <para>The CAS authentication extension is packaged as a
<filename>.tar.gz</filename>
+ file containing only the extension itself,
+
<filename>guacamole-auth-cas-0.9.11-incubating.jar</filename>, which must
--- End diff --
I believe this is 0.9.12 as of the latest rebase.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
