Bug 56727 – Assignment of VLAN-ID by Radius should be configurable per network or ip-range

Bug 56727 - Assignment of VLAN-ID by Radius should be configurable per network or ip-range


Summary:	Assignment of VLAN-ID by Radius should be configurable per network or ip-range

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Radius
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-10-11 18:07 CEST by Wolfgang Bayrhof
Modified:	2023-10-11 18:07 CEST (History)
CC List:	0 users

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?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2023100521000247
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 Wolfgang Bayrhof

2023-10-11 18:07:54 CEST

Currently there is the recommendation to configure only one VLAN-ID for each user directly or via a group object, since the result of an LDAP search order cannot be influenced by the radius-server.

Customer requests the ability to configure more than one VLAN-ID per user, maybe dependable from a network object or an ip-range. Or perhaps with a configurable filter or something similar.

The customer uses also UCS@school and there it's possible to configure teachers who are assigned to more than one school. With a feature like described the customer would get the ability to avoid a second account for teachers working on two schools.