Some EPP servers do not maintain a strict one-to-one mapping between EPP client IDs and Registrar IDs. So for example, if a client that logs in to an EPP server using <clID>ClientX</clID> and then creates an object, the object may contain <clID>RegistrarX</clID> instead of <clID>ClientX</clID>.
To account for this situation, we need to define new input parameters:
epp.registrarId01epp.registrarId02
Test subjects whose EPP servers do not have a 1:1 mapping can specify the "Registrar ID" value that will appear in the <clID>, <crID>, <upID>, <reID> and <acID> elements in EPP responses, instead of the Client ID.
Internal refs: NRRST-1573 & NRRST-1574
Some EPP servers do not maintain a strict one-to-one mapping between EPP client IDs and Registrar IDs. So for example, if a client that logs in to an EPP server using
<clID>ClientX</clID>and then creates an object, the object may contain<clID>RegistrarX</clID>instead of<clID>ClientX</clID>.To account for this situation, we need to define new input parameters:
epp.registrarId01epp.registrarId02Test subjects whose EPP servers do not have a 1:1 mapping can specify the "Registrar ID" value that will appear in the
<clID>,<crID>,<upID>,<reID>and<acID>elements in EPP responses, instead of the Client ID.Internal refs: NRRST-1573 & NRRST-1574