Problem Direct Entitlement

Hi everyone
i’m developing dps direct entitlement and was having a problems
I've followed the tutorial for the testing of direct entitlement on adobe tv
all according to those in the tutorial adobe tv, start from signinwithcredentials, entitlement and verifyEntitlement
The following result
but when i test on my android app can’t log in and there is an error “that username and password did not work. Double check them and try again.”
why it could happen? and please give a solution

Did you register your integrator ID with Adobe? I suggest you call enterprise support for assistance, they're good at tracking down problems with entitlement server implementations.
Neil

Similar Messages

Problems with Direct Entitlement API ( problems to download the issuenumbers and others)

Hi there.
Here we are using the last version of Direct Entitlement API , we had download on this url : http://www.adobe.com/devnet/digitalpublishingsuite/articles/direct-entitlement-starter-kit .html
But We are getting some problems
With https://dev01.cartacapital.com.br/adobe/api/entitlements.php?authToken=0fc82ad9b9c11703ad5 c8dee47d7ee26&appVersion=1.3.1&appId=468573252
This api is modificated to show only the issuenumbers that I have the right to read.
I'm getting this results
<result httpResponseCode="200">
<entitlements>
<productId>com.editoraconfianca.revistacartacapital.edicao753</productId>
<productId>com.editoraconfianca.revistacartacapital.edicao754</productId>
<productId>com.editoraconfianca.revistacartacapital.edicao755</productId>
<productId>com.editoraconfianca.revistacartacapital.edicao756</productId>
<productId>com.editoraconfianca.revistacartacapital.edicao757</productId>
<productId>com.editoraconfianca.revistacartacapital.edicao758</productId>
<productId>com.editoraconfianca.revistacartacapital.edicao759</productId>
<productId>com.editoraconfianca.revistacartacapital.edicao760</productId>
<productId>com.editoraconfianca.revistacartacapital.edicao761</productId>
<productId>com.editoraconfianca.revistacartacapital.edicao762</productId>
<productId>com.editoraconfianca.revistacartacapital.edicao763</productId>
<productId>com.editoraconfianca.revistacartacapital.edicao764</productId>
</entitlements>
</result>
That's ok
But on my Ipad ( for testing only) , show this entitlement on a first place, on top of my screen.
1) Why does the app is showing others entitlements too, like ( com.editoraconfianca.revistacartacapital.edicao752, 751 ... ) ?
2) When I try to download all the result in my xml , is not allowed to donwload, but the ( com.editoraconfianca.revistacartacapital.edicao752, 751 ... ) is allowed to download
When I verify if I can download the issue ( https://dev01.cartacapital.com.br/adobe/api/verifyEntitlement.php?authToken=0fc82ad9b9c117 03ad5c8dee47d7ee26&appId=com.editoraconfianca.revistacartacapital&productId=com.editoracon fianca.revistacartacapital.edicao753&appVersion=1.0.34 )
show this result
<result httpResponseCode="200">
<entitled>true</entitled>
</result>
But I can't do the download.
Help Please.

There is no license or serial number for the DVD installer.
If you can get access to a Mac with a working DVD Drive, make the DVD into a .dmg file in Disk Utility and then copy the .dmg file onto a USB key and install onto your Mac from that.
Peter

Direct Entitlement Problems

Hey Everyone,
I have a direct entitlement system that somewhere between registering user and authenticating within the app. I have confirmed that my Intergrator ID is valid, and that the "Send app ID and version" box is checked in the app builder.
The system has been up for a while but I had to modifiy it, which is when I noticed that the system was broken. After some digging I found that the SSL cert on https://lighthouse.adobe.com was and remains invalid. I managed to write my system around the invalid cert, but I'm worried that it might still be causing problems.
I've contact Gold support, but they have not been helpful (they have yet to even issue a case number).
I'm on deadline and very much need this system to work. Any help is appriciated.
-Scott

Hi Scott - Contact me directly at [email protected]
But, whatever your service is, you shouldn't be using anything on lighthouse.adobe.com.

Direct entitlement V30

Hi Everyone,
I have a simple direct entitlement system build into an app. It works perfectly fine if I build my app as a V29 viewer. When I update to V30, users are unable to log in. They get the message saying there is a "problem connecting to the server at this time, please try again later." I know that there were some changes made to the direct entitlement system (as referenced here: Changes to Direct Entitlement infrastructure) but I'm not sure of the impact. So please forgive my ignorance here, but does anyone understand the change that is referenced in the article and how to implement a fix to my system that will make it compatible with a V30 viewer.
Thanks
-Scott

You should call Gold Support for assistance with this. They can walk through debugging steps to find out why it isn't working with your configuration.
Neil

Troubleshooting direct entitlement sign in

I'm trying to troubleshoot the sign in process for our enterprise app that uses direct entitlement. We had this working without ssl, and accessing the URLs and passing parameters rturns the xml expected when using a browser.
Now that we have applied ssl to our server the app has issues, yet the server isn't showing any certificate errors.
looks like I may have the same issue as these caps, http://forums.adobe.com/message/4758851#4758851
Charlse hasn't revealed anything useful as yet - or I'm not understanding what I am looking at.
Any help appreciated

I asked an engineer about this. One possibility is that the name on the SSL certificate does not match the subdomain name contained within the URL. If you're running Java7, another possibility is a problem with the defaults on Java7. To resolve this issue, you're better off contacting your Adobe representative.

Your Direct Entitlement Service Exception

Dear All,
I have the problem with Entitlement Server.
i was read the tutorial : Your Direct Entitlement Service | Adobe Developer Connection and test it with : Digital Publishing Suite Help | Test your Direct Entitlement API V2
This is the result :
https://www.anakku.id/V2/api/entitlements?uuid=postman&appId=net.anakku.majalah&appVersion =0.1&authToken=54196d77d45c10b…
<result httpResponseCode="200">
<entitlements>
<productId>net.anakku.majalah.mediakit1</productId><productId>net.anakku.dps_retail</productId>
<productId>net.anakku.majalah.perdana.iphone</productId>
<productId>net.anakku.majalah.mediakit</productId>
</entitlements>
</result>
And if i test wiht verifyEntitlement :
 
Fatal error: Uncaught exception 'Exception' with message 'String could not be parsed as XML' in /home/anakku/public_html/V2/api/verifyEntitlement.php:62
Stack trace:
#0 /home/anakku/public_html/V2/api/verifyEntitlement.php(62): SimpleXMLElement->__construct('')
#1 {main}
thrown in
/home/anakku/public_html/V2/api/verifyEntitlement.php on line
62
 
Fatal error: Uncaught exception 'Exception' with message 'String could not be parsed as XML' in /home/anakku/public_html/V2/api/verifyEntitlement.php:62 Stack trace: #0 /home/anakku/public_html/V2/api/verifyEntitlement.php(62): SimpleXMLElement->__construct('') #1 {main} thrown in/home/anakku/public_html/V2/api/verifyEntitlement.php on line 62
verifyEntitlement
(Method:GET)
https://anakku.id/V2/api/verifyEntitlement?uuid=postman&appId=net.anakku.majalah&appVersio n=0.1&authToken=54196d77d45c10…
Result:
 
Fatal error: Uncaught exception 'Exception' with message 'String could not be parsed as XML' in /home/anakku/public_html/V2/api/verifyEntitlement.php:62
Stack trace:
#0 /home/anakku/public_html/V2/api/verifyEntitlement.php(62): SimpleXMLElement->__construct('')
#1 {main}
thrown in /home/anakku/public_html/V2/api/verifyEntitlement.php on line 62 
Whats wrong in this framework or configuration ?
Thanks
Message was edited by: HARDIONO PUSPONEGORO

When you did the test call for verifyEntitlement did you correctly include proper XML? That exception is saying the XML you sent wasn't valid.
Neil

Adobe DPS: Direct Entitlement API Version 2

Hi guys,
I have some questions about Direct Entitlement API Version 2 (http://download.macromedia.com/pub/developer/dps/entitlement/direct-entitlement-api.pdf). Based on the API, SignInWithCredentials and entitlements request body will contain a XML document which contains information like email address, passwords, product IDs and cover dates. I'm able to get the email address and password from the parameter but I could not retrieve the product IDs and cover dates at all. Is it because we do not have a valid Integrator ID from Adobe yet?
Any help would be greatly appreciated.
Thank you.
Regards,
Gary.

Yes, I understand that I need to create a web services for these URLs. My main concern is how can I use Direct Entitlement API Version 2 in Sprint 26 only.
I have listed out the major differences between API version 1 and API version 2. I have also list out how I retrieve the data from my web services.
For SignInWithCredentials URL:
According to API version 1, emailAddress, password, appId, appVersion and uuid are passed in the queries using HTTP GET method. But in API version 2, emailAddress and password are in the request body as a XML document using HTTP POST method.
I built my app in Sprint 26 but I retrieved the emailAddress, password, appId, appVersion and uuid using HTTP GET methods only. My request body and HTTP POST methods are both empty.
For entitlements URL:
According to API version 1, the transaction must be done by HTTP GET method. It does not provide folios' product ID and cover date either. But in API version 2, the transaction must be done by HTTP POST method and it will provide folios' product ID and cover date in the request body as a XML document.
I built my app in Sprint 26 but I retrieved the authToken, appId and appVersion using HTTP GET method only. My request body and HTTP POST method are both empty.
It seems that in my app is still using API version 1. How can I use API version 2 for my app in Sprint 26?
You can get both API version from these links:
API version 1: http://download.macromedia.com/pub/developer/dps/entitlement/Entitlements_API.pdfAPI version 2: http://download.macromedia.com/pub/developer/dps/entitlement/direct-entitlement-api.pdf
Thank you.
Regards,
Gary.

Direct Entitlement API

Hi,
I've created a web service based from the direct entitlement api v2 - http://download.macromedia.com/pub/developer/dps/entitlement/direct-en titlement-api.pdf
Based from my testing, it passed the specification based from the API document.
All methods were created. The service is a .net web service (.asmx) and methods are below.
https://<website>/dps/entitlement.asmx/verifyEntitlement
https://<website>/dps/entitlement.asmx/SignInWithCredentials
https://<website>/dps/entitlement.asmx/RenewAuthToken
https://<website>/dps/entitlement.asmx/entitlements
What Service URL/Service Auth URL should I be using? I tried using https://<website>/dps/entitlement.asmx/ (with slash) and https://<website>/dps/entitlement.asmx (no slash) but both are not working.
Is there a way I can troubleshoot, like seeing what code from the dps app is consuming the web service to know if it really can connect to the service or see what error might be there?
Thanks!

Thanks for all replies. I was able to figure out what's causing the error using Charles proxy tool. Looking at the errors, pointed me to the issue of the integrator version. I just created the service having the specifications mentioned in the latest version of the integrator. The latest integrator details can be found here (direct-entitlement-api.pdf) - http://www.adobe.com/devnet/digitalpublishingsuite/articles/dps-entitlement.html
This issue is closed.

How to get "Request Body" in Direct Entitlement API ?

According to the API version 2 (http://download.macromedia.com/pub/developer/dps/entitlement/direct-entitlement-api.pdf), it said the Request Body contain the following xml document specifiying the user credentials
<credentials>
 <emailAddress>[email protected]</emailAddress>
 <password>stupid</password>
</credentials>
How can I get this xml in PHP? e.g. $_POST['credentials'] or somthing else?

And also this xml inside "/entitlements":
Request Body: The request should contain the following xml document.
<folios>
 <folio>
 <productId>com.bonnier.flying.10.01.2010</productId>
 <coverDate>2011-10-11T20:49:40Z</coverDate>
 </folio>
 <folio>
 <productId>com.bonnier.flying.11.01.2010</productId>
 <coverDate>2011-11-11T20:49:40Z</coverDate>
 </folio>
</folios>
Or how can I get testing requests from Adobe for the API development?

Recent Safari problem - direction arrows in bookmark bar have disappeared. Help please. I am on a MacBook (white) running OS 10.6.9 with Safari 5.1.10

Recent Safari problem - direction arrows in bookmark bar have disappeared. Help please. I am on a MacBook (white) running OS 10.6.9 with Safari 5.1.10

cd,
From the Safari Menu Bar, choose View>Show Toolbar:

Direct entitlement custom distribution

We're building direct entitlement server for our corporate (enterprise distribution) clients.
Can we distribute different folios to several different groups? (So that our groups are not just everyone and subscribers)
Do you recommend some third party software for this? Portico?

This was not about Apple's certificates or their Enterprise license.
I want to build app that through dps sign in can download different content for different users (or user groups) for example Country 1 folios, Country 2 folios etc. I read somewhere that direct entitlement subscribers can be controlled through xml but I don't know how complex variations can be made.

V25 and Direct Entitlement

We have 15 apps in the app store using direct entitlement and it has been working well for over a month.
In testing some upgraded versions using v25 in the App Builder, those apps seem to be unable to Sign In.
Have there been changes to the Entitlement API? If so, where can I find documentation on those changes?
UPDATE: Never mind. User error on our part. v25 is fine in this respect.

Please check the difference between the Android and iOS Entitlement Application details. Where can I set the entitlement server on the Android application? On iOS it is the 'Service URL'. Thanks.

Can I change "purchased" label on folios within a direct entitlement app?

When using the enterprise edition to set up direct entitlement, the end user gets the note "purchased" next to the folio the are entittled to. Is it possible to change this to "available" or similar? In B2B applications it's likely that no money would change hands and the "purchased" label could lead to some confusion.

Hi Stu,
Yes it's possible. Use Customized Strings feature of the DPS App Builder.
You can customize all strings stored in the viewer in all supported languages. For example, you can customize button text in the library and text in dialog boxes. Select this option, and then click Generate Template to download an XML template to your Documents folder. You can then edit this XML file and specify it in DPS App Builder. If you’re editing a viewer created for a previous version, download and edit the newest template for best results.
When you edit the XML file, each UI element includes a <key name> and one or more language strings (such as <en> for English). Edit the text in the language code (such as <en>); do not change the <key name> string.
Regards,
Gennady

Direct Entitlement request form

Hi,
I've made the setup for the DPS Entitlement Server following this guide:
How to install the DPS Entitlement Server | Adobe Developer Connection
The setup_check.html page returns everything ok.
I am about to fill this form to get Adobe's feedback and my Integrator ID:
http://download.macromedia.com/pub/developer/dps/adobe_dps_direct_entitlement_request_form .pdf
Where can I send it ? to who ?
thanks a lot!

Thank you Vik,
Actually its almost impossible to contact any support by phone from here (swiss)
anyway I am lucky enought to find this post from Storycode in the morning:
Code Corner: Adventures in DPS Entitlement | Storycode
Thanks to them they explain a bit more clearly where to send this form
Once you’ve filled out the form, email it to [email protected], including the following info in the body of the message:
1. a friendly request for Direct Entitlement whitelisting
2. your Service URL
3. your Integrator ID
4. that your Direct Entitlement Server is API version 2
5. your test username and password
Hope this can help
Flo

Direct Entitlement API documentation

Hi,
My company just purchased DPS a while ago.
I'd like to ask where we can find documentation on how to integrate into the direct entitlement API's, we are planning to control access to our folios through our own authentication system.
Thank you.

I know this is an old discussion. For the sake of those searching the web and forums for answers with keywords, i'd like to update here with links to documenations and and API's
Direct Entitlement API documentation: http://download.macromedia.com/pub/developer/dps/entitlement/direct-entitlement-api.pdf
Direct Entitlement starter kit: http://www.adobe.com/devnet/digitalpublishingsuite/articles/direct-entitlement-starter-kit .html
Landing page to all entitlement related doumentation: http://www.adobe.com/devnet/digitalpublishingsuite/entitlement.html

Problem Direct Entitlement

Similar Messages

Maybe you are looking for