Is your feature request related to a problem? Please describe.
Users are starting to use pyracf without ensuring all setup steps are complete like the IRR.IRRSMO00.PRECHECK profile that we document. Without this profile, alter profile requests result in empty return values from IRRSMO00, which pyracf does not handle gracefully as shown:
File "/usr/lpp/IBM/cyp/v3r10/pyz/lib/python3.10/site-packages/pyracf/user/user_admin.py", line 295, in set_passphrase
result = self.alter(userid, traits={"base:passphrase": passphrase})
File "/usr/lpp/IBM/cyp/v3r10/pyz/lib/python3.10/site-packages/pyracf/user/user_admin.py", line 801, in alter
return self._make_request(user_request, irrsmo00_precheck=True)
File "/usr/lpp/IBM/cyp/v3r10/pyz/lib/python3.10/site-packages/pyracf/common/security_admin.py", line 178, in _make_request
results = SecurityResult(result_xml)
File "/usr/lpp/IBM/cyp/v3r10/pyz/lib/python3.10/site-packages/pyracf/common/security_result.py", line 13, in __init__
self.__result = XMLParser.fromstring(result_xml)
File "/usr/lpp/IBM/cyp/v3r10/pyz/lib/python3.10/site-packages/defusedxml/common.py", line 127, in fromstring
return parser.close()
File "/usr/lpp/IBM/cyp/v3r10/pyz/lib/python3.10/xml/etree/ElementTree.py", line 1724, in close
self._raiseerror(v)
File "/usr/lpp/IBM/cyp/v3r10/pyz/lib/python3.10/xml/etree/ElementTree.py", line 1624, in _raiseerror
raise err
xml.etree.ElementTree.ParseError: no element found: line 1, column 0
Describe the solution you'd like
This should result in a new error that should also steer users to this documentation to correct this mistake on their own.
Describe alternatives you've considered
Writing errors this severe to a log file of some sort could also be beneficial.
Is your feature request related to a problem? Please describe. Users are starting to use pyracf without ensuring all setup steps are complete like the IRR.IRRSMO00.PRECHECK profile that we document. Without this profile, alter profile requests result in empty return values from IRRSMO00, which pyracf does not handle gracefully as shown:
Describe the solution you'd like This should result in a new error that should also steer users to this documentation to correct this mistake on their own.
Describe alternatives you've considered Writing errors this severe to a log file of some sort could also be beneficial.
Additional context N/A