Changes to PartnerSystemUser SOAP endpoint

Hello there fellow community members!

I just wanted to share with you a minor change coming to our System User flow, specifically the PartnerSystemUserService endpoint response - used for obtaining system user credentials from a signed system user token.

The change is the actual XML response. If you are using standards based approach to obtaining an element value from the XML you should be OK and good to go. 

The current response format (in Production)

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
  <s:Body>
    <AuthenticationResponse xmlns="http://www.superoffice.com/superid/partnersystemuser/0.1">
      <IsSuccessful>true</IsSuccessful>
      <Token>eyJhbGciOiJSUzI1N...aoWt_o82-EHEUQ</Token>
      <ErrorMessage i:nil="true" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"/>
    </AuthenticationResponse>
  </s:Body>
</s:Envelope>

The future response format: (currently available for testing in SOD)

<Envelope
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:xsd="http://www.w3.org/2001/XMLSchema"
	xmlns="http://schemas.xmlsoap.org/soap/envelope/">
	<Body>
		<AuthenticationResponse xmlns="http://www.superoffice.com/superid/partnersystemuser/0.1">
			<IsSuccessful>true</IsSuccessful>
			<Token>eyJhbGciOiJSU...ibT0XkIQ</Token>
			<ErrorMessage xsi:nil="true" />
		</AuthenticationResponse>
	</Body>
</Envelope>


If you are using the system user functionality in production, we highly recommend you verify it is working as expected in the SOD environment now, otherwise you may problems when this new format goes into production.  Estimated arrival in production is May 9th (just a few days away).

Best regards!

Noch keine Antworten!