Bug 56248 – Missing NameID Format results in incorrectly transmitted NameID value

Bug 56248 - Missing NameID Format results in incorrectly transmitted NameID value


Summary:	Missing NameID Format results in incorrectly transmitted NameID value

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	SAML
Version:	UCS 5.0
Hardware:	All 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-07-03 11:54 CEST by Christian K
Modified:	2023-07-17 09:40 CEST (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 Christian K

2023-07-03 11:54:49 CEST

When adding a new SAML- SP to the "UCS SAML Identity Provider", the field "Format of NameID attribute" does not contain a default value.
If this is not being changed (left empty), the NameID attribute is not being transmitted correctly (it seems as if a random ID is being transmitted). Upon changing the format (e.g. to "urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified"), the NameID Attribute is transmitted with the correct (as per LDAP) value.

Setting a default like "urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified" and/or making this a required field would resolve this issue.