Bug 32564 – Move mapping functionality to UDM syntax classes

Bug 32564 - Move mapping functionality to UDM syntax classes


Summary:	Move mapping functionality to UDM syntax classes

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UDM (Generic)
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 minor with 1 vote (vote)
Target Milestone:	UCS 3.x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-09-11 16:38 CEST by Lukas Walter
Modified:	2020-07-03 20:56 CEST (History)
CC List:	4 users (show)

See Also:	43129 27844
What kind of report is it?:	Development Internal
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):	Cleanup
Max CVSS v3 score:

Attachments
Suggested Patch for syntax.Base64Upload (10.75 KB, patch) 2013-09-11 19:57 CEST, Arvid Requate	Details \| Diff
View All 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 Lukas Walter

2013-09-11 16:38:12 CEST

We should check wheter it could be useful to integrate the whole mapping mechanism into the UDM syntax classes (see Bug #30342).

Comment 1 Arvid Requate

2013-09-11 19:56:33 CEST

Well, maybe not *all* but certainly map/unmapBase64.

Comment 2 Arvid Requate

2013-09-11 19:57:15 CEST

Created attachment 5425 [details]
Suggested Patch for syntax.Base64Upload

Comment 3 Arvid Requate

2013-11-04 13:25:37 CET

As far as I saw, currently the syntax parse/totext methods are only called by the udm-cli. So, before changing anything here, the UMC module udm would need to be modified to send the udm properties through these syntax layer methods. The basic idea is

User <-> UMC/CLI <-syntax.parse/totext-> <-> UDM module/foo <-mapping-> LDAP

This way, we would have the UDM property data independent of the encoding.

Comment 4 Ingo Steuwer

2020-07-03 20:56:30 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.