CAS Client Liaison
Description
The CAS Client Liaison position is focused on coordinating CAS Server development with the maintainers of the various CAS clients. This position is critical as CAS is only as useful as the community can utilize the features provided, which requires CAS client support.
Tasks
Understand latest CAS protocol changes and ramifications
Communicate changes to CAS client maintainers
Communicate needs and concerns to CAS server developers
Follow up on security concerns reported by the community
Own cross-client-library documentation / webpages / wiki pages
Required Skills
Familiarity with CAS protocol and architecture
Good communication skills
Time Commitment
Initial CAS Server development iteration to identify changes affecting CAS clients
Subscription to JASIG security mail list to keep up to date on security concerns with CAS clients
Comments
We do have a general purpose security listserv, which is publicized on our site. Anyone can send a concern/issue/question to it. It's monitored by a subset of project developers. I assume that there's CAS representation on that list. Are you on it, Scott? Would it suffice for this individual to just be added to this list?
I am on the list. Once we identify a client liaison (if we do) they should probably be added to.
I'm having some difficulties with the Time Commitment section as it seems like there needs to be an avenue for the community to report security concerns. If we had a mail list or an email address that could forward emails to this individual, then they could monitor that and handle as they come in. Otherwise, the time commitment is related to what kind of changes are going on in the server side mostly.
Thoughts?