Difference between revisions of "Development/Functional testing/Single sign-on (CAS) tests"
| Line 1: | Line 1: | ||
| − | {{#pagetitle: | + | {{#pagetitle: Single sign-on (CAS) tests }} |
[[Main Page]] > [[Development]] > [[Development/Functional testing]] > Development/Functional testing/Single sign-on (CAS) tests | [[Main Page]] > [[Development]] > [[Development/Functional testing]] > Development/Functional testing/Single sign-on (CAS) tests | ||
Revision as of 17:05, 9 September 2020
Main Page > Development > Development/Functional testing > Development/Functional testing/Single sign-on (CAS) tests
About
Centralized Authentication Service (CAS) is an enterprise single sign-on protocol that can be implemented by enabling the arCasPlugin and by registering user accounts with a CAS server. For more about CAS see https://www.apereo.org/projects/cas.
For testing purposes, a public CAS demo server can be used. See https://django-cas-ng-demo-server.herokuapp.com/cas/) s. The username/pw combo admin / django-cas-ng can be used to authenticate on the demo server.
The arCasPlugin also provides an optional mechanism for dynamically setting AclUserGroup membership on each login, based on the presence or absence of expected values in the attributes returned from the CAS server during p3/serviceValidate (CAS version 3.0 only).