another day another test: this multi device route just worked in this direction:
PC: sign out of library, sign in wth overdrive [ all of that in chrome browser] , checkout and download an epub book ( which then appears in ADE library on the PC )
now go to tablet, to libby, find my loans, try reading that book: it worked.
it would be so mush easier to understand this stiff if I knew a little bit more about what goes on under the bonnet: e.f. when on the PC I signed in with my overdrive account, why did the book go to ADE anyway. Is overdrive just a container format ( a bit like MKV) and its actually using adobe security under the bonnet ? it must be as I can see an new ascm licence file for that book created in "my downloads" , left there by using chrome browser to run the process. [ i looked inside that acsm but it does not show my adobe ID in clear anywhere, it has a gibberish looking auth code - like <fulfillmentToken fulfillmentType="loan" auth="user" xmlns="http://ns.adobe.com/adept">
<distributor>urn:uuid:f1227b83-f91b-4f30-9ae2-0f65ffeea9ac</distributor>
so is overdrive using "my" adobe ID - the one in my PC's registry, that I know the credentials for, or does it create one of its own, known to any device that I sign into overdrive on?.
Last edited by stumped; 11-20-2017 at 12:53 PM.
|