CAS auth¶

Table of Contents¶

CAS auth 1

Introduction 1

What does it do? 1

About this manual 1

Users manual 2

Administration 2

Known problems 2

To-Do list 2

Changelog 2

Introduction¶

Users manual¶

Nothing to doc.

Administration¶

This extension has several requirements:

• CAS server running and validating users.
• LDAP server record created inside the site sys folder.

After this requirements, admin only has to create a record inside any sys-folder with the type: CAS server. Typo3 will ask for the following fields:

• Hide . Is checked the server will be hidden.

• Server name: Base url to create the complete url to CAS server (without the protocol and the uri). For example: “ mydomain.com ”

• Server port: For the moment, only 80 and 443 are supported. The port determines the protocol: http or https. For example, “443”.

• Path to the log: CAS auth wites to log, so the paht to the log must be passed. Important: path should be correct and it should have write permissions. For example, “ access ”.

• CAS servlet: Uri to create complete url to CAS server.

• URL passed to CAS to come back to Typo3 after login . For example:

  index.php?id=alias_to_home&submit=Login&logintype=login

• URL passed to CAS to come back to Typo3 after logout . For example:

  index.php?logintype=login&submit=Logout

With the examples written before, the complete url for CAS could be:

https://mydomain.com/access?L=0&service=http://baseURL/index.php?id=a lias_to_home%26submit=Login%26logintype=login

Known problems¶

CAS doesn't allow multi-domain sites configured over the same Typo3 instance.

To-Do list¶

• Multidomain support.
• Delete port parameter and allow to user add http:// or https:// directly at “Server name” parameter.

Changelog¶