Bug 1564593

Summary:	replace xmlSecSoap* functions with lasso implementations
Product:	[Fedora] Fedora	Reporter:	John Dennis <jdennis>
Component:	lasso	Assignee:	John Dennis <jdennis>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	28	CC:	jdennis, rcritten, ssorce
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	lasso-2.5.1-13.fc28	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-12 18:20:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Dennis 2018-04-06 17:31:15 UTC

xmlsec1 1.2.21 removed Soap support which Lasso utilizes (e.g. xmlSecSoap* symbols).

xmlsec1 1.2.22 restored Soap for Lasso

xmlsec1 1.2.24 deprecated Soap 

xmlsec1 1.2.25 added --enable-soap configure option to build soap support, however soap is still deprecated and will be removed in a future release.

Therefore the only sensible thing is to remove Lasso's dependence on xmlSecSoap and re-implement the functionality in Lasso.

Comment 1 Fedora Update System 2018-05-02 22:35:45 UTC

lasso-2.5.1-13.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-3fcce95800

Comment 2 Fedora Update System 2018-05-03 20:23:01 UTC

lasso-2.5.1-13.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-3fcce95800

Comment 3 Fedora Update System 2018-05-12 18:20:01 UTC

lasso-2.5.1-13.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.