Bug 29949 – Policies need to be moved to /var/cache

Bug 29949 - Policies need to be moved to /var/cache


Summary:	Policies need to be moved to /var/cache

Status:	CLOSED FIXED

Product:	Z_Univention Corporate Client (UCC)
Classification:	Unclassified
Component:	User logins
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal
Target Milestone:	UCC 1.0
Assigned To:	Moritz Muehlenhoff
QA Contact:	Lukas Walter

URL:
Keywords:	interim-3

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-01-07 14:18 CET by Moritz Muehlenhoff
Modified:	2013-03-26 09:14 CET (History)
CC List:	0 users

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Moritz Muehlenhoff

2013-01-07 14:18:06 CET

During login the user and client policies are fetched with the machine account credentials and stored in /tmp.

This needs to be moved to /var/cache (and the session script adapted) so that the policies are also available if the UCC client is used offline.

Comment 1 Moritz Muehlenhoff

2013-01-07 16:46:03 CET

The policies are now stored in /var/cache/ucc and the RDP and UCC session scripts have been adapted to that path.

Comment 2 Lukas Walter

2013-01-10 16:40:59 CET

OK -> Policies are stored unter /var/cache/ucc/
OK -> Policies are stored for each user who has logged in at least once
OK -> Users can log in working offline using the stored login credentials

Verified.

Comment 3 Moritz Muehlenhoff

2013-03-26 09:14:41 CET

UCC 1.0 has been released: 
http://forum.univention.de/viewtopic.php?f=26&t=2417
http://forum.univention.de/viewtopic.php?f=54&t=2418

If this error occurs again, please use "Clone This Bug".