News

All News

June 27, 2017

Shibboleth is an identity provider that uses the CalNet Central Authentication Service (CAS) screen to provide access to services hosted outside the University. While CAS is used directly by onsite services such as CalCentral, Shibboleth was designed for off-site services such as Google, Box, BearBuy, ServiceNow, Zoom, and thousands of other services like wikis and forums.

Shibboleth’s recently released Consent Module adds a layer of user consent to the release of attributes from CalNet to the service you are trying to access.

May 12, 2017

Ever wonder what CalNet is up to?

CalNet maintains a Service Projects board with current and future projects sorted by priority and roughly laid out on a 1, 3 and 5 year timeline. This RoadMap enables the campus community to see what we are working on, to provide feedback, and help prioritize efforts. The board is public and can be viewed at:

https://trello.com/b/UhEcXglh/calnet-service-projects

March 20, 2017

Due to recent major upgrades of the Identity Management environment, CalNet accounts for former students, employees and affiliates have not been expired since October 4, 2016. Account expiration and the accompanied notifications were turned back on last week. Moving forward, users with accounts that should be expired will start receiving grace notifications by email. Grace period end dates will be set to July, so that sufficient notice can be given to these users.

The CalNet expiration process is as follows:

February 23, 2017

For years, newly admitted students at Cal had to wait overnight to complete their onboarding tasks, such as creating their CalNet ID and passphrase. The delay was due to an overnight batch process in which new student data was migrated from Student Information Systems (SIS) to CalNet overnight, before a UID could be produced.

The UID is a Unique ID. Every campus user, whether student, staff, faculty, guest, or affiliate, has a UID. The presence of a UID allows a user to create a CalNet ID.

Students must wait no more.

December 22, 2016

Dear campus community,

Due to the recent major upgrade of the Identity Management environment, CalNet accounts for former students, employees and affiliates have not been expired since October 4, 2016. We are working towards releasing new software early this spring to resume account expiration. We anticipate these changes to go into effect in mid-March 2017, but that date is subject to change.

The CalNet expiration process will be as follows:

November 29, 2016

In conjunction with our recently released CalNet Account Manager (mycalnet.berkeley.edu), CalNet is launching a campus-wide campaign to ensure that users are able to take advantage of cool new self-service tools. In order to use the tools at mycalnet.berkeley.edu, students and staff need first submit a personal Recovery Email Address via mycalnet.berkeley.edu.

September 16, 2016

To developers and the technical community,

On October 4, 2016, the CalNet team will retire the legacy LDAP Sync Code and hand control of LDAP provisioning to the Berkeley Person Registry. This step modernizes campus identity data management and will affect the services described below.  Please take note.

Sync Code Retirement - why it’s a big deal!

August 2, 2016

CalNet has done it again! Recently released by your favorite Identity and Access Management team, CalNet Account Manager (CAM) is an exciting new tool that allows you to manage your CalNet account, yourself. Previously, students and employees needed to contact the Cal1Card office or a campus CalNet deputy to get a token to create a new CalNet account or reset a forgotten passphrase. This new application lets you make these changes yourself. It also serves as a central location for making changes to personal or security information, streamlining the process for all users.

June 15, 2016

CAS, LDAP, MFA, UID -- what's it all mean?

Review our CalNet Glossary to find CalNet terms and definitions to help you better understand the world of Identity and Access Management.

June 2, 2016

CalNet operates a complex suite of applications that support the Identity and Access Management functions of the University.  As technology is updated throughout the CalNet portfolio, updates appear on this the CalNet Release Notes page: https://calnet.berkeley.edu/node/195

If you support technology that depends on CalNet tools, this is the best place to look to see if something in the CalNet technology stack has changed or will change, and how it could be affecting your services.

April 20, 2016

On Monday, May 16, 2016, CalNet will deprecate all legacy CAS service names. On that date, the only name that will resolve to a production CAS server will be the auth.berkeley.edu name in the DNS. 

March 7, 2016

On Friday, February 19, guests representing a plethora of UC Berkeley web applications came together in University Hall to experience the fun-filled extravaganza that was CalNet’s “CAS-a-Nova.” Following opening words from Paul Rivers, Chief Information Security Officer, and an informative presentation by Jeremy Rosenberg, Manager of the CalNet Identity and Access team, attendees had the opportunity to get to know the faces of CalNet as well as begin the process to set up custom CAS Authorization.

February 5, 2016

CalNet has launched a new website.

New sections include CalNet for Technologists, CalNet for Departments and CalNet for Me. We hope the new layout and organization makes it easier to find the information you need!

Send feedback to calnet-coordinator@berkeley.edu.

February 4, 2016

Update - see it online!

https://youtu.be/jnKMIouBSWw

If you couldn't attend CAS-a-Nova in person on Feb. 19, check it out online at https://youtu.be/jnKMIouBSWw.

February 2, 2016

March 14, 2014

If you work on a project team, how do you keep track of team members so that you can send information, share files and schedule meetings? In our current environment, we typically have to create and maintain a group list in each of the different applications that support our administrative needs (such as bMail, Box, Calshare, etc.). Wouldn’t it be more efficient to create a group once and have it appear automatically in the applications we use?