Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Main Scenario Extensions Notes References Associated Modules Implementations Advice and ExperienceContributors

Goal: Support CAS authentication to Sakai
Version: ?
DG Priority: ?
Status: partially implemented
Scope: ?
Preconditions: ?
Success end: A deployer can easily configure Sakai to offer "Log in via CAS" the or one of the ways users authenticate to Sakai.
Failed end: ?
Actors: ?
Primary Actor: ?
Trigger: ?
Security Concerns: ?
Logging: Sakai should log the login of users and record the way in which the user authenticated (awp9 logged in at TIMESTAMP via CAS).
Performance Concerns: ?

Main Success Scenario

End user visits Sakai. Sakai offers a "Log in via CAS" button. User clicks button, authenticates to CAS, CAS redirects back to Sakai. Sakai validates service ticket, establishes user session, context, etc., user is authenticated to and logged into and begins using Sakai.

Extensions

References

See CAS website / JA-SIG

Associated Modules

Implementations

Advice and Experience


Contributors

Name <email>

Institution

Notes

Andrew Petro<andrew.petro@yale.edu>

Yale University

initial notes

  • No labels