Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
go
go
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • SRCT
  • gogo
  • Issues
  • #162

Closed
Open
Opened Sep 19, 2017 by Daniel W Bond@dbond2Developer
  • Report abuse
  • New issue
Report abuse New issue

Option to require CAS authentication to resolve links

Summary

A professor sharing a link with their class can see the number of times that their link has been clicked through, but cannot see whether that's a couple of people opening the link at various times, or if it has been opened by all of their students.

On Blackboard, professors can see who has viewed pages and files, and that's what we're aiming to recreate here.

If a box or radio (pick your poison) is selected when a link is created (and then optionally modifiable afterwards), begin redirecting links through CAS, storing student usernames provided in the response (to be later viewed on the detail link page), only then sending the student to the link.

Helpful Links

check out the cas_callback.py file for additional CAS information

Edited Jun 03, 2018 by David Haynes
Assignee
Assign to
2.3
Milestone
2.3
Assign milestone
Time tracking
None
Due date
None
Reference: srct/go#162