Bug 56493 – Log output of 91univention-saml.inst is hard to read if it fails

Bug 56493 - Log output of 91univention-saml.inst is hard to read if it fails


Summary:	Log output of 91univention-saml.inst is hard to read if it fails

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Join (univention-join)
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2023-08-28 16:41 CEST by Christina Scheinig
Modified:	2023-09-01 20:12 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Feature Request
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?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2023082821000191
Bug group (optional):	SAML, Troubleshooting
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 Christina Scheinig

2023-08-28 16:41:24 CEST

We introduced debugging code with Bug 44669.
Now the joinscript spams with debug information if it failes. The obvious messages like
Password policy error: is too simple.
or E: object not found
are lost in too many messages.
We should make this configurable, otherwise the support needs to modify the joinscript for decreasing these messages.

In my opinion this was not a very helpful decision!

Comment 3 Arvid Requate

2023-09-01 20:12:49 CEST

Also, the debug output was added for a reason.
We should look into the output case by case.