Provision list of entitlements AEOS

:bangbang: Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.

Hi everyone,

We’ve set up a web service connector for AEOS applications (SOAP API), and we’re running into an issue with provisioning multiple entitlements of the same entitlement type.

The challenge: whenever we try to add an entitlement, the operation replaces all existing authorizations a user has.
For example:

  • User has an access profile with entitlement 1

  • We provision an access profile with entitlements 1 and 2

  • Result: the user ends up only with 2, as the previous authorization gets overwritten.

We tested with both addRemoveEntInSingleReq: false and addRemoveEntInSingleReq: true, but the behavior remains the same.

Here’s a simplified snippet of the SOAP request body we’re sending:

<soapenv:Body>
  <sch:ProfileChange>
    <sch:CarrierId>$plan.nativeIdentity$</sch:CarrierId>
    <sch:AuthorisationOnline>
      <sch:TemplateAuthorisation>
        <sch:Enabled>true</sch:Enabled>
        <sch:TemplateId>$plan.entitlement$</sch:TemplateId>
        <sch:DateFrom>2025-01-12T00:00:00</sch:DateFrom>
      </sch:TemplateAuthorisation>
      <sch:TemplateAuthorisation>
        <sch:Enabled>true</sch:Enabled>
        <sch:TemplateId>$plan.entitlement$</sch:TemplateId>
        <sch:DateFrom>2025-01-12T00:00:00</sch:DateFrom>
      </sch:TemplateAuthorisation>
    </sch:AuthorisationOnline>
  </sch:ProfileChange>
</soapenv:Body>

Notes:

  • The application does not support appending a template.

  • This means the full list of entitlements must be sent in every request.

My question:

  • Is there a way to pass multiple entitlements of the same type in the request body?

  • If not, are there any known workarounds for this limitation?

Any insights or experiences would be greatly appreciated!

You can modify the body with a before operation rule to add the other entitlements in there as well.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.