Adobe Access 4.0 - Supported devices

Hi,
Does anyone have a list of all the devices which support Adobe Access 4.0? I've been navigating through these forums and I didn't seem to find any reliable one.
Thanks in advance.

We do support Adobe Access feature in Flash Player and AIR on desktop such as Windows and Mac OS X.
Also, AIR on Android does.
For iOS devices, Android devices, we do have a native library for Adobe Access feature.
If you have any other specific questions, please try to contact Adobe person via http://www.adobe.com/products/adobe-access.html
The page has contact form and phone number.
Thanks,
Hiroshi

Similar Messages

Adobe Access Protection on iOS devices?

I am having an issue in terms of Adobe Access not supported in iOS. I have been developing a custom player along with a bunch of other back end Adobe Technologies only to find out now that protection is not available in iOS.
DRMManager.isSupported returns false when we test the app in iOS Simulator. DRMManager.isSupported returns true when we use Air Simulator.
I am using OS X 10.9, AIR SDK 4.0, Apache Flex 4.11.0, and Xcode 5.02, and Flash Builder 4.7.
This is a huge problem and amounts to false advertisement because the protection is supposed to be handled by Adobe AIR which is supposed to be uniform across platforms. If protection is not supported on iOS, then the appeal of write one code for multiple platforms is not there any more.
I don't understand why protection is not uniformly supported if the same Adobe Air is installed on both iOS and Android devices. I also don't understand why HDS is supported on Android but not on iOS devices. It makes no sense. The whole reason for using Adobe AIR is to not have to deal with the specifics of each platform.
We were supposed to go live on Jan 1st, but had to postpone to deal with several issues. Now it seems that we may have to reevaluate the decision to use Adobe technologies altogether.
Any suggestions from Adobe would be appreciated.

Your comments on point 3 are sobering and kind of a slap in the face to someone who has been developing a streaming app with the idea that Adobe Air has 99% reach in the desktop and mobile market. I went back to the Http Dynamic Streaming and Adobe Access pages to find the restrictions that I missed when I was deciding on the technologies to use.
The only hint of not being able to use HDS or OSMF on iOS was the omission that Adobe Access protection could be delivered via Adobe Air on iOS devices as shown in the first image below of the Adobe Access technical specs.
On the other hand, there all kinds of statements and illustrations that would make you believe otherwise, especially on mobile devices.
No explicit statement can be found that says that HLS is the only way to stream content to iOS devices, that the OSMF framework is HLS agnostic, and that one has to build an iOS native app from scratch if they want to consume protected HLS. I guess not smth you want to put on a page where you want to market a product.
In building a native app, how do I make up for the lost functionality that comes by default with AIR such as the integration of Adobe Access in AIR, DRM Management, SWF verification, etc.
As it stands, the OSMF framework is a half-baked solution as it cannot be used on iOS devices because it is HLS agnostic….although some folks have written plugins to enable OSMF to consume HLS.
I am currently testing a plugin to see if I can consume protected HLS. If I fail then I will scrap the entire project…which also means not buying Adobe Access or Adobe Media Servers. Neither will I be looking at Adobe Primetime.
My OSMF based app is able to consume HLS content when I debug in AIR Simulator. Testing on iOS simulator or iOS devices has yet to prove successful. Something breaks inside AIR when it is compiled using iOS SDK.
The reason why I chose Adobe technologies is because it seemed like all the pieces were there to put together a streaming solution that fit my business model. I did not want to have to write everything and Adobe technologies promised a quick time to market. Now 7 months later I am finding out that perhaps I should have read the Adobe Access technical specs with the precision of a lawyer.
In my testing, protected content cannot be consumed in AIR unless DRMManager class is available. In help.adobe.com we read the following:
“The DRMManager manages the retrieval and storage of the vouchers needed to view DRM-protected content. With the static DRMManager.getDRMManager() method, you can access the existing DRMManager object to perform the following DRM-management tasks:
Preload vouchers from a media rights server, using a DRMContentData object.
Query the local cache for an individual voucher, using a DRMContentData object.
Reset all vouchers (AIR only)
AIR profile support: This feature is supported on all desktop operating systems and AIR for TV devices, but it is not supported on mobile devices. You can test for support at run time using the DRMManager.isSupported property.”
Using OSMF 2.0 framework, I have been able to take advantage of both PHDS and Adobe Access protection schemes in my Flex based app running on Adobe Air on Android. In Android Devices, DRMManager .isSupported returns true.
In iOS, it seems to be a whole different story. As I said in my first post, DRMManager.isSupported returns false when testing via iOS Simulator but returns true when testing via Air Simulator. So the attack vector idea that you put forward cannot stand because if that was true it would require DRMManager.isSupported to be false in all debugging scenarios not just on iOS Simulator or iOS devices.
The behavior of the app in iOS simulator and Air Simulator is not consistent when it comes to responding to touch based events and rendering visual elements as well. Performance and functionality degrades even more when testing directly on iOS devices. All iOS devices exhibit the same symptoms. For example, trying to select a list item is almost impossible….item renderers simply do not respond when one tries to select an item.
No such symptoms or differences exist between AIR Simulator and Android devices. So, it seems to me that there are AIR to iOS compilation issues when a mobile air app is packaged through iOS SDK. Smth brakes inside of AIR during packaging. I believe that this is the reason why DRMManager.isSupported returns false when testing app in iOS simulator and devices.

Adobe Access on iOS.

This discussion is a follow up of my previous discussion that can be found at http://forums.adobe.com/message/6174242. I am starting a new discussion for clarity.
The previous discussion addressed the question of whether Adobe Access DRM and its variant PHLS are available on iOS. The answer is NO, Unless You Sign UP for Adobe Primetime.
You have to sign up for Adobe Primetime to get the iOS Primetime Player SDK which includes the Adobe Access iOS APIs needed to stream PHLS in a native iOS app.
The Adobe Primetime platform requires a large monthly commitment, so that means that for all practical purposes Adobe Access DRM and PHLS is available only to a small number of companies.
The Adobe Access iOS API used to be part of the Adobe Access SDK but at some point was removed from the SDK.
The Adobe Access website (http://www.adobe.com/products/adobe-access.html) continues to market Adobe Access as follows:
“Publish and protect video streams carrying studio-grade content to desktops, connected TVs, tablets, and smartphones, including iOS and Android devices, using a single DRM platform”.
After talking to several Adobe folks, the picture that is emerging is one of bait and switch. It is clear that at some point, Adobe decided to remove the Adobe Access iOS API from the Adobe Access SDK and make the iOS API part of the Adobe Primetime iOS SDK. This is a fact. The question is why?
Only Adobe can answer that question, but it is safe to assume that this was a strategic decision. By removing the iOS API from the Adobe Access SDK, companies that want to deliver protected content to iOS devices have to sign up for Adobe Primetime.
Adobe seems to have gone to some length to implement this strategic decision.
It did not update the publicly available OSMF 2 to be able to consume Adobe Access protected HLS streams. Development of OSMF 2 was stopped in 2010.
It removed support of DRMManager class and Netstream class members (required for DRM) from AIR for iOS.
It removed the Adobe Access iOS API from the Adobe Access SDK. I am not sure when this was done, but the Adobe SDK sent to me last August does not include the iOS API.
Adobe has not published any documentation on how Adobe Access DRM for HLS is implemented.
The deception consists in the fact that Adobe is still marketing Adobe Access in a way that makes you believe that Adobe Access DRM is available on iOS devices. This is false.
Purchasing Adobe Access alone is not enough to protect content on iOS devices. The Adobe Access SDK does not include the iOS API.
The question is then why does Adobe continue to promote such deception.
Again, this has to be a strategic decision….a classical example of bait and switch. Who in the right mind would develop around a half-baked product from the get go knowing that they would not be able to deliver protected content on iOS devices.
The Adobe Access team has admitted that Adobe Access DRM and its variant PHLS are only available through Adobe Primetime iOS Player but the Adobe Access site continues to make false claims. This is deception.
Of course, Adobe knows that by declaring no support for iOS, Adobe Access and Adobe Media server sales would be in danger. But that is the right thing to do both morally and legally.
In my scenario the only right action is for Adobe to provide the Adobe Access iOS API. It’s too late for Adobe to say oops sorry. I have already agreements with content owners which specify Adobe Access as the protection scheme. All the encoding and packaging is based on Adobe Access and it’s variant PHLS. If Adobe does not provide the iOS API, I will be forced to seek the appropriate legal action.

Hello,
Adobe Access DRM on mobile devices is only provided by Adobe via the Primetime SDK. You can get more information on Primetime, as well as contact Adobe on becoming a Trial user, here: http://www.adobe.com/solutions/primetime.html
cheers,
/Eric.

Adobe Access - new drmNativeInterface.framework for iOS 8

Hi,
We are a company that has been using Adobe Access for more than a year and so far we are very happy with the fact that the Adobe Access 4 can support playback DRM content on Desktop / Android and iOS without any problem.
But recently, to prepare for the upcoming iOS 8, I have upgraded my development iPhone 5 and iPad 2 to the iOS 8 Beta and the drmNativeInterface.framework starts working wrongly. Sometime I can stream my DRM HLS content, sometimes, the drmNativeInterface.framework just stuck in the middle without any error or exception (this issue happens quite frequently like 7 out of 10 times). After debugging line by line, followings are the piece of code that make the framework stucked without any error or exception.
1. The framework sometime stops working when we try to get the singleton instance of DRMManger
_drmManager = [DRMManager sharedManager];
2. Sometime it stops when we try to parse the M3U8 url:
[_drmManager getUpdatedPlaylist:m3u8Url
                                      error:drmErrorHandler
                                    updated:^(NSURL * newPlaylist, DRMMetadata * newMetadata){
                                        NSLog(@"Update M3U8 URL Player list for license process");
                                        //Successfully retrieved the metadata from provided link
                                        m3u8PlayList = newPlaylist;
                                        _metadata = newMetadata;
3. Sometime it stops where the DRMSession is initialized (after the User Authentication process is completed)
_session = [_drmManager
                        createDRMSession:_metadata
                        playlist:m3u8PlayList
                        error:^(NSUInteger majorCode, NSUInteger minorCode, NSError *platformError) {
                            NSLog(@"Failed to get DRM Session");
                        complete:^{
                            NSLog(@"Successfully obtained DRM Session");
Most of the time, it stops when we try to get the singleton instance of DRMManager ( issue number 1 )
I can ensure that the framework works very well with iOS6 and iOS7 (although iPhone 4 with iOS7 crashes while a lot during the DRMSession initialization).
If there is new version of drmNativeInterface.framework, please kindly let me know where we an get it as the drmNativeInterface.framework we have been using is quite old (for iOS5 I think).
Thank you very much.
Jack

Same reply would apply to you.
Do you have Adobe sales contact? If so, you may want to contact him/her.
If not, can you send an email me directly with your company information. I'll try to figure it out.
my address is : [email protected]
Thanks,
Hiroshi

Why is adobe flash player not supported?

Why is adobe flash player not supported?

Because.
Apple and Adobe could never come up with an OS that liked flash and a version of flash that worked on the OS. So never the twain will meet. and now Adobe is abandoning mobile flash in favor of other things, so it's become a moot point.
With the surge in the number of mobile devices and the fact that a lot of them don't use flash, site creators will need to take mobile devices into account when they create their sites and assess their accessibility.

Does Adobe Access DRM work on Roku?

Does Adobe Access DRM work on Roku? If not, is there support planned for it in the near future ?
The Adobe Primetime press release states Roku as a supported platform. Does this mean Adobe Access DRM will be supported on Roku ?
Thanks,
- Abey

Hi Abey,
Currently, we don't support Access on Roku, but we are actively working on expanding our device coverage.
- Stephen

What is the Adobe Access DRM (version 5.2) "External CEK" feature?

[ Prior to Access 5.2 ]
The randomly-generated (or user-provided) Content Encryption Key is encrypted using an asymmetric "license server key" and then stored in the content's metadata. The CEK is never required to be persisted anywhere else (like a Key Management system or secure database). When a client device makes a license request, the content metadata is sent to the Access DRM License Server, which has the private asymmetric key needed to decrypt the CEK out of the metadata. The license server can then issue a license to the client containing this CEK. For more details on the entire workflow, please see this post: DRM Packaging and License Issuance Lifecycle/Workflow
[ New Feature introduced in Access DRM 5.2 - External CEK ]
Due to popular demand, version 5.2 of Access DRM introduced a new Key Retrieval scheme called "External CEK". The reason this name was chosen is because the CEK is now external from the metadata (where it traditionally resided). Instead of the encrypted CEK being stored in the content metadata, a CEK-ID is stored there instead. When the license server is processing a license request, if it detects that the KeyRetrievalType of the request is of type "ExternalKeyRetrieval", then the license server must implement logic to do a retrieval of the CEK, which is specific to the company using Access DRM. The key retrieval may be via a KeyManagementService, a SecureDatabase, or even something as simple as a locally-stored flat file (hopefully only for testing purposes).
Using internal-CEK or external-CEK is transparent to the client device; no code has to change (or has to change if you're upgrading from an earlier version of Access). The only changes needed to incorporate External-CEK into your Access DRM workflow is to make a change on the content packaging side (to enable E-CEK and specify the CEK-ID), and on the license server side (to recognize the KeyRetrieval type as E-CEK and then do a CEK fetch).
Details on how to integrate the External-CEK workflow into your Adobe Access DRM infrastructure is included in your Adobe Access v5.2 documentation and DVD.
cheers,
/Eric.

Thanks! Will automatic update select ‘Adobe Reader X’ after support ends for ‘Adobe Reader 9.5.5’ on June 23, 2013?

Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved. It started with the last upgrade to 10.8

Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved. It started with the last upgrade to 10.8

Back up all data.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
resetpassword
That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

I would like to know how to get refunded when my iTunes account was accessed from an unusual device.

I received a receipt for a purchase I did not make in the store. It's for a single $1.29 ringtone. The same day I received an email saying my account had been accessed from a different device than was usual. I followed the directions and change my password but I want to know if my account will be credited back the $1.39 for the ringtone I did not purchase.

Contact iTunes Customer Service
Use this Link > Apple Support iTunes Store Contact

I am running InDesign CS5.5 and trying to open an In Design File but getting an error message. " Cannot open the file "PDavidLCover.indd". Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file

I am running InDesign CS5.5 and trying to open an In Design File but getting an error message. " Cannot open the file "PDavidLCover.indd". Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file me be open in another application."Please help I really need to get this file open.

Since you've shown us the folder contents it's a good bet it isn't in use (no lock file). And it doesn't look like the file is mis-named as there doesn't seem to be anything else there that would be the .indd file (but just in case, open it in TextEdit and paste the first few lines here so we can see what the file header says), so the most likely case is the file is damaged. Is that on a removable device of some sort?
You can try the tool at Repair corrupt InDesign Adobe files on Mac OS X or send me a link to the file by private message and I'll try the recovery tool I have for Windows.

How to install adobe digital editions on android device (zt pad)

how to install adobe digital editions on android device (zt pad)

I don't think ADE will itself run on Android.
You need to install an app such as Bluefire (free) which supports DRM epub books.
Make sure you authorise it with the same AdobeID you use on the PC or to buy books.
You can get books on the PC with ADE, download them, 'sideload' the .epub files to the tablet using a file manager such as Windows Explorer, and read them on Bluefire.
For library books, the Overdrive app (free) should allow you to borrow, doanload and read books with no need for a PC or ADE.

An error occurred while trying to access the Apple Wireless Device

Hello All;
I just bought an Airport Extreme Base Station today and am all ready having problems. I am running a PC. I connected a Motorola DSL model to the Airport's QAN port and then I connected the computer to one of the Ethernet ports. When I first loaded the software that came with it, things worked perfectly and I was able to connect to the internet. Then, when I opened up the configuration file, and try to enter the configuration manually, I receive the error ... "An error occurred trying to access the Apple Wireless Device. Make sure your network connection is valid and try again". When I try to open the Manual setup I get that error. Also why are the "settings" always grayed out ? I am connected ot the Internet but can't understand why I can't do a manual setup or change any of the settings. I reset my passwords and need to change them again but am unable to do that. Thanks for any help and advice you can give me.
Tim

I am about to return this unit to the store I bought it at. I keep getting an error 6753 whenever I try to do any kind of configuration. Most of the configuration options are grayed out in the setup utility anyway. There is a ton of stuff about this problem on the internet. There are a few solutions offered like modify the tcp/ip properties but I sure can't figure out what they're talking about. Not everyone who buys this is going to be tech savvy.
I'll call tech Support tonite and if they can't offer a permanent soultion, I'm returning the Airport Extreme and separate dsl modem tomorrow and getting a wireless dsl router specifically designed for the PC.
Tim

Adobe flash player not support in android 4.1.2 samsung s2

Plz give me feedback (private contact info removed by moderator). i have Samsung S2 Mobile. And i have android 4.1.2(Lastest S2 Version). I can install this software. but I cant see any LIVE TV CHANNEL. EveryWhere flash player required. And i READ somewhere that in ADOBE FLASH PLAYER not SUPPORT in Samsung S2 Mobile. Sir plz SOLVE THIS PROBLEM AS SOON AS POSSIBLE.
SIR PLZ GIVE ME FEEDBACK...
-THANK YOU SO MUCH...

There is no more Flash Player for Android and there won't be another. Android is no longer compatible with Flash Player. Playing Flash content is very processor consumptive and it drains your battery, also shortening the life of it. Android (Google) recommends using either "Dolphin" or "Puffin" as your browser if you need to view Flash content with a mobile device running Android. They're both free in the GooglePlay store. These browsers use "server side" rendering to reduce the load on your device.

I've lost my access code for my device and the type of device is the iPad Mini

I lost my access code from may device and the type of device is the ipad mini

iOS: Device disabled after entering wrong passcode
http://support.apple.com/kb/ht1212
How can I unlock my iPad if I forgot the passcode?
http://tinyurl.com/7ndy8tb
How to Reset a Forgotten Password for an iOS Device
http://www.wikihow.com/Reset-a-Forgotten-Password-for-an-iOS-Device
Using iPhone/iPad Recovery Mode
http://ipod.about.com/od/iphonetroubleshooting/a/Iphone-Recovery-Mode.htm
Saw this solution on another post about an iPad in a school enviroment. Might work on your iPad so you won't lose everything.
~~~~~~~~~~~~~
‘iPad is disabled’ fix without resetting using iTunes
Today I met my match with an iPad that had a passcode entered too many times, resulting in it displaying the message ‘iPad is disabled – Connect to iTunes’. This was a student iPad and since they use Notability for most of their work there was a chance that her files were not all backed up to the cloud. I really wanted to just re-activate the iPad instead of totally resetting it back to our default image.
I reached out to my PLN on Twitter and had some help from a few people through retweets and a couple of clarification tweets. I love that so many are willing to help out so quickly. Through this I also learned that I look like Lt. Riker from Star Trek (thanks @FillineMachine).
Through some trial and error (and a little sheer luck), I was able to reactivate the iPad without loosing any data. Note, this will only work on the computer it last synced with. Here’s how:
1. Configurator is useless in reactivating a locked iPad. You will only be able to completely reformat the iPad using Configurator. If that’s ok with you, go for it – otherwise don’t waste your time trying to figure it out.
2. Open iTunes with the iPad disconnected.
3. Connect the iPad to the computer and wait for it to show up in the devices section in iTunes.
4. Click on the iPad name when it appears and you will be given the option to restore a backup or setup as a new iPad (since it is locked).
5. Click ‘Setup as new iPad’ and then click restore.
6. The iPad will start backing up before it does the full restore and sync. CANCEL THE BACKUP IMMEDIATELY. You do this by clicking the small x in the status window in iTunes.
7. When the backup cancels, it immediately starts syncing – cancel this as well using the same small x in the iTunes status window.
8. The first stage in the restore process unlocks the iPad, you are basically just cancelling out the restore process as soon as it reactivates the iPad.
If done correctly, you will experience no data loss and the result will be a reactivated iPad. I have now tried this with about 5 iPads that were locked identically by students and each time it worked like a charm.
~~~~~~~~~~~~~
Try it and good luck. You have nothing more to lose if it doesn't work for you.
 Cheers, Tom

Cannot play Adobe Access Protected Content in Chrome (version 30 and higher); Error 3321/3322?

Symptom:
An end-user cannot play Adobe Access protected content. The client application returns a persistent 3321 (Individualization Error) or 3322 (Device Binding Failure) error code.
Root Cause in Chrome Browser:
Adobe Access DRM must create a unique machine identifier (I.e. "token") to identify the the device. This token is provided to the Adobe Access license server during a license request to view DRM protected content. If Chrome Browser disables the ability for Adobe Access DRM to create a unique machine identifier, playback of Protected Content will fail with a 3321 or 3322 error code. By default, this setting is enabled and available to toggle in Chrome Browser version 30 and higher. Unchecking this option will prevent Adobe Access DRM from properly functioning. A 3321 or 3322 error that persists after a call to resetDRMVouchers is an indicator that this setting may need to be changed.
Resolution:
In your Chrome settings:
•             Click on "Show advanced settings…"
•             In the subsequent "Privacy" section, click on "Content settings…"
•             In the subsequent "Protected Content" section, make sure that the following box is checked "Allow identifiers for protected content (computer restart may be required)".
We are working with Google to allow better detection of this condition, so that the client will return a 3368 (User cancelled or user settings disallow operation) error code when the box is unchecked.

Symptom:
An end-user cannot play Adobe Access protected content. The client application returns a persistent 3321 (Individualization Error) or 3322 (Device Binding Failure) error code.
Root Cause in Chrome Browser:
Adobe Access DRM must create a unique machine identifier (I.e. "token") to identify the the device. This token is provided to the Adobe Access license server during a license request to view DRM protected content. If Chrome Browser disables the ability for Adobe Access DRM to create a unique machine identifier, playback of Protected Content will fail with a 3321 or 3322 error code. By default, this setting is enabled and available to toggle in Chrome Browser version 30 and higher. Unchecking this option will prevent Adobe Access DRM from properly functioning. A 3321 or 3322 error that persists after a call to resetDRMVouchers is an indicator that this setting may need to be changed.
Resolution:
In your Chrome settings:
•             Click on "Show advanced settings…"
•             In the subsequent "Privacy" section, click on "Content settings…"
•             In the subsequent "Protected Content" section, make sure that the following box is checked "Allow identifiers for protected content (computer restart may be required)".
We are working with Google to allow better detection of this condition, so that the client will return a 3368 (User cancelled or user settings disallow operation) error code when the box is unchecked.

Adobe Access 4.0 - Supported devices

Similar Messages

Maybe you are looking for