Description of problem:

Support staff is in the UI and is about to change a group or user or some other
complex object they don't understand.  They click a button and get an LDIF
backup of the object.  They attach the "before" LDIF to the ticket.  They make
the change.  They click a button and get an LDIF backup of the object.  They
attach the "after" LDIF to the ticket.

People can now audit the change in the future.

They could also, after severe warning prompts, import the original "before"
LDIF which would drop the current object and replace it with that one.

^We currently do a similar workflow when working with clients in RHSSO.  It
isn't something that is 'needed' in the core sense of the word.  But having it
allows the IAM team to let more general and lesser trained support desks do
some stuff while both sides feel more at ease about it and learn and recover
from mistakes quicker.

A button that shows the raw LDIF in the GUI along with the command and/or API
call to get it would be cool as a teaching tool as well.  Something like
https://petstore.swagger.io/#/  but show ipa user-show and the API call, etc.




Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: