October 1th - October 2th, 2022 / Release notes

Was this article helpful?

Still need help? contact us

Comments

8 comments

  • Avatar
    Tobias Månsson
    inriver champion

    Breaking change in the deploy.

    If you used version 1.0.1 of the POST fetchdata method, you need to downgrade again to 1.0.0 

    Not working: https://<cluster-specific-url>.productmarketingcloud.com/api/v1.0.1/entities:fetchdata 

    Working: https://<cluster-specific-url>.productmarketingcloud.com/api/v1.0.0/entities:fetchdata 

    0
  • Avatar
    Srini Kaila

    Is BETA change to support user creation using Rest API available for everyone? What should we to participate in that if it is not open.

    Is there any documentation available?

    1
  • Avatar
    Mark Stuart-Walker

    There is mention about about v1.0.1 above yet the website shows v1.0.0. Is 1.0.1 in BETA release?

     

    Swagger https://api-prod1a-euw.productmarketingcloud.com/swagger/ui/index#/Channel 

    0
  • Avatar
    Srini Kaila

    I managed to setup new permission for User Provision and use API call to add user.

    However, when I add user using the API, I do not see that user added to Control Center and user is also unable to unable to logon.

    0
  • Avatar
    Emilia Nilsson
    business solutions architect

    Hi Srini Kaila,

    The API for User is to provision a user in order to synchronize SAML accounts across systems, and not add an actual user to inriver. The use case for this is to provision users in a single sign-on situation, where it otherwise would get the default role only once they log in and role re-assignment would be done ad-hoc.

    The Swagger documentation will give you a bit more insight into what it does: https://api-prod1a-euw.productmarketingcloud.com/swagger/ui/index#!/System/System_ProvisionUser 

    Kind regards,
    Emilia

    0
  • Avatar
    Srini Kaila

    Hi Emilia Nilsson, we have SSO activated and the user is authenticating through SSO when trying to logging in to inriver. However, they see "Unexpected Error". They are not seeing the access of "default" role.

    When I used Provision User method, I also supplied the Segment ID and the Role name that is supposed to be assigned to that user.

    Now, if I call GET method to inquire on that user, I see inriver response with correct Segment ID and Role Name (as I gave in Provision User call originally). 

    0
  • Avatar
    Emilia Nilsson
    business solutions architect

    Hi Srini Kaila

    This seems like an issue that would require further investigation - may I ask you to create a support ticket and provide the customer name and details in it?

    Kind regards,
    Emilia

    1
  • Avatar
    Srini Kaila

    Thanks Emilia Nilsson
    I submitted a ticket already (#50568) after my initial comment. 

    0

Please sign in to leave a comment.