Skip to content
This repository has been archived by the owner. It is now read-only.

On-demand de-provisioning. #96

Closed
macosforgebot opened this issue Dec 15, 2006 · 8 comments
Closed

On-demand de-provisioning. #96

macosforgebot opened this issue Dec 15, 2006 · 8 comments

Comments

@macosforgebot
Copy link

@macosforgebot macosforgebot commented Dec 15, 2006

@wsanchez originally submitted this as ticket:111


Principal and calendar home resources need to be de-provisioned somehow. See #⁠25 for how I expect it to work, based on the directory service.

What's presently missing is handling the case where a disabled user is re-enabled with a new GUID (meaning it's a new user with the same short name). Right now, the new user sees the old user's data.

Moving to 2.x for the rest.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Dec 15, 2006

@wsanchez originally submitted this as comment:1:⁠ticket:111

  • Milestone changed from Preview 1 to Later
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Feb 23, 2007

@wsanchez originally submitted this as comment:2:⁠ticket:111

  • Status changed from new to assigned
  • Milestone changed from Later to Version One
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Aug 1, 2007

@wsanchez originally submitted this as comment:3:⁠ticket:111

  • Milestone changed from 1.0 to 1.1

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Dec 15, 2007

@wsanchez originally submitted this as comment:4:⁠ticket:111

  • Milestone changed from 1.1 to 1.2
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Mar 10, 2008

@wsanchez originally submitted this as comment:5:⁠ticket:111

  • Milestone changed from 1.2 to 2.x
  • Description modified

More fixes via #⁠231.

I think the only remaining item is to decide what should happen to meetings involving dead accounts.

If a dead account is an attendee, it's may be OK to leave things be. If, however, a dead account is an organizer, that's a problem, since attendees need to know that the meeting organizer is gone (which implies that the meeting should go away), and particularly because resources/rooms/etc. could remain booked when they should be freed up.

We may need a more explicit deletion step for that, since it would modify data irreversibly. The current de-provisioning can be undone by re-adding the account, but this would actually cancel meetings.

Perhaps a caladmin tool to list and/or remove de-provisioned accounts.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Oct 26, 2009

@wsanchez originally submitted this as comment:6:⁠ticket:111

  • Milestone changed from CalendarServer-2.x to CalendarServer-3.x
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Aug 1, 2011

@wsanchez originally submitted this as comment:7:⁠ticket:111

  • Radar deleted
  • Status changed from assigned to closed
  • Milestone changed from CalendarServer-3.x to CalendarServer-3.1
  • Resolution changed from to Software changed

New calendarserver_purge_principals tool in 3.0 is how we're solving this.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Aug 1, 2011

@wsanchez originally submitted this as comment:8:⁠ticket:111

  • Milestone changed from CalendarServer-3.1 to CalendarServer-3.0
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.