#550 Remove/deprecate BtoA() and AtoB()
Closed: fixed Opened by edewata.

The CMS.BtoA() and CMS.AtoB() have a dependency on CMSEngine which makes it unusable by clients. These methods call the some other methods in CMSEngine which eventually call base64encode() and base64decode() in Utils. It's actually possible to call the Utils method directly and get the same results.

It's not clear whether the indirection via CMSEngine is necessary. One possibility is to allow custom engine to use different encoding, but the problem is it might not match the client's encoding.

One solution is to change all code that calls CMS.BtoA() and CMS.AtoB() to call the Utils methods directly, and remove/deprecate the BtoA() and AtoB() in CMS and CMSEngine.


[06/04/2014] - Moving to Milestone 10.3 due to schedule restrictions.

Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

The methods no longer exist in PKI 10.6.

Metadata Update from @edewata:
- Custom field proposedmilestone adjusted to None (was: Future)
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @edewata:
- Issue assigned to edewata

Metadata Update from @edewata:
- Issue set to the milestone: 10.6.8 (was: UNTRIAGED)

Metadata Update from @edewata:
- Assignee reset
- Issue set to the milestone: UNTRIAGED (was: 10.6.8)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1120

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata