Hi Guy, Congratulations on your set-up of a CAS server.
Sharing your documentation is a fine way to contribute and to ease the path for others. I encourage you to share your documentation. There are many common casual ways to ease into sharing notes and documentation about CAS. For instance, you could * create an account at wiki.jasig.org and share your document via your personal wiki space. This makes your documentation available on the Web and even discoverable from within Jasig's wiki. * Put your documentation into a Google Document, set permissions appropriately broadly upon it, and post a link to that document on this list. That's got some interesting collaboration potential and is a format more like what it sounds like you've currently got. * Blog somewhere you're comfortable, and post a link to that to this list. There are also more formal and directly-within-the-project ways to contribute to documentation. You might offer edits to the wiki documentation or the documentation in source control and included in the CAS server software distribution, for instance. All the ways of contributing are valuable. A lot of the value is in sharing at all, so I do hope I'll have a chance to read over your document. Congratulations on your CAS server implementation and on your customizations. Kind regards, Andrew On Wed, Oct 31, 2012 at 4:03 AM, Guy Thomas <[email protected]>wrote: > I finished my first (basic) set-up of a CAS server and two CAS clients. In > order to organize the information I found on the CAS site, in the mailing > list and on the internet I created a document (MS-Word and PDF). It also > contains some questions left after the initial set-up.**** > > ** ** > > I don’t know if people in this list struggling with a first set-up might > be interested. If that’s the case, I’ll gladly share the information with > you as is. Of course, you have to be aware that the document can and > certainly will contain incorrent statements, assumptions, etc. Maybe an > experienced CAS administrator could go through the document and correct the > most obvious flaws.**** > > ** ** > > If people are interested, what’s the best way to distribute the > information in the document?**** > > ** ** > > The set-up has two special “features”:**** > > **· **A user who wants to log in has to provide a “domain” next to a > username and a password. A domain is a protected environment on the web, > for example an extranet.**** > > **· **Authenticating a user is realized by means of a (SOAP-based) > web service. A client layer for this web service is integrated in the CAS > server. This can be considered an indirect variant of JDBC authentication. > **** > > ** ** > > ** ** > > ** ** > > Guy Thomas**** > > Analist-Programmeur**** > > Dienst Projecten en Ontwikkelingen**** > > ** ** > > Provinciehuis**** > > Provincieplein 1**** > > 3010 Leuven**** > > ** ** > > Tel: 016267945**** > > ** ** > > > ------------------------------ > Aan dit bericht kunnen geen rechten worden ontleend. Alle berichten naar > dit professioneel e-mailadres kunnen door de werkgever gelezen worden. In > het kader van de vervulling van onze taak van openbaar belang nemen wij uw > relevante persoonlijke gegevens op in onze bestanden. U kunt deze inzien en > verbeteren conform de Wet Verwerking Persoonsgegevens van 8 december 1992. > > Het ondernemingsnummer van het provinciebestuur is 0253.973.219 > > -- > You are currently subscribed to [email protected] as: [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
