Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

DPS2014 subscribers to DPS2015

Avatar

Level 2

Hi,

We  plan to migrate the DPS2014 to DPS2015. Before we had the Entitlement Server with under DPS2014.

What we did is, on publish builder I  enabled the Direct Entitlement Server option and filled the IntegratorID (I got this for DPS2014 v.2). But it seem not , the Entitlement testing from postman said 401. Any guide how to do this?

Thanks,

1 Accepted Solution

Avatar

Correct answer by
Employee

If your DPS 2014 direct entitlement services references DPS 2014-specific items such as accounts or folio names, you'll need to make adjustments to get your entitlement service to work with DPS 2015. For example, you should use Product IDs instead of folio names. Here are a couple of resources:

Digital Publishing Solution Help | Set up direct entitlement in DPS 2015

Digital Publishing Solution Help | Use the Content Producer Service API to access collection and pro...

View solution in original post

2 Replies

Avatar

Correct answer by
Employee

If your DPS 2014 direct entitlement services references DPS 2014-specific items such as accounts or folio names, you'll need to make adjustments to get your entitlement service to work with DPS 2015. For example, you should use Product IDs instead of folio names. Here are a couple of resources:

Digital Publishing Solution Help | Set up direct entitlement in DPS 2015

Digital Publishing Solution Help | Use the Content Producer Service API to access collection and pro...

Avatar

Level 2

What about for the new and fresh installation using Entitlement Server and DPS2015. One of our new client they started using DPS this month, the Entitlement Server already setup, tried the SignIn calls is working fine with auth code, but when they call the entitlements service it return 401 status.

Thanks,