You're viewing help content for version:
- 6.4
- Older Versions
Note:
To download AEM Screens Player, click here.
AEM Screens is also available in Google Play, iTunes App Store, and Chrome OS.
For implementation of Chrome OS Player, see Chrome Management Console for more information.
Note:
Important:
AEM Screens player does not make use of the Cross-Site Request Forgery (CSRF) token. Therefore, in order to configure and AEM server to be ready to use for AEM Screens, skip the referrer filter by allowing empty referrers.
The following key points below helps to configure and AEM server to be ready to use for AEM Screens:
Allow Empty Referrer Requests
Follow the steps below to enable the Apache Sling Referrer Filter Allow Empty. This is required for optimal operation of the control protocol between AEM Screens Player and AEM Screens server.
- Navigate to Adobe Experience Manager Web Console Configuration
- Check the allow.empty option.
- Click Save.
AEM in NOSAMPLECONTENT runmode
Running AEM in production uses the NOSAMPLECONTENT runmode. Remove the the X-Frame-Options=SAMEORIGIN header (in the additional response header section) from
http://localhost:4502/system/console/configMgr/org.apache.sling.engine.impl.SlingMainServlet.
This is required for the AEM Screens Player to play online channels.
Password Restrictions
AEM Screens Player registration will fail, if the password restrictions are set.
Remove the following config to set it correctly,
Dispatcher Configuration
For Dispatcher, add client headers to .any file. Allow the following headers through:
- "X-Requested-With"
- "X-SET-HEARTBEAT"
- "X-REQUEST-COMMAND"
Note:
Recommendation:
It is recommended to use HTTPS for AEM Screens Server in production use.
-
Click iTunes App Store to download AEM Screens for iPad.
Note:
If you leave the Resolution field empty, it will use the native resolution of the device.
-
Download OS X player from AEM Screens Player Downloads.
-
Download Android Player from AEM Screens Player Downloads.
The devices registration process is done on 2 separate machines:
- The actual device to be registered, for example your Signage Display
- The AEM server that is used to register your device
-
Note:
To get more information on creating a new project for Screens in the AEM dashboard, see Creating and Managing Screens Project.
In AEM, the device should be added to the list and remain unassigned. To learn how to assign it, see Device Assignment.
Before, you learn device assignment, it is recommended you have prior knowledge on how to:
System wide user password restrictions might cause failure in the device registration. The device registration uses a random generated password to create the device user.
If the password is restricted by the AuthorizableActionProvider configuration, creating the device user might fail.
Note:
The current generated random password is composed of 36 ASCII characters, ranging from 33 - 122 (includes almost all special characters).
When the device registration fails, check the AuthorizableActionProvider configuration to see if there are any restrictions.
The following error logs show failed device registration:
25.09.2016 16:54:03.140 *ERROR* [59.100.121.82 [1474844043109] POST /content/screens/svc/registration HTTP/1.1] com.adobe.cq.screens.device.registration.impl.RegistrationServlet Error during device registration
javax.jcr.nodetype.ConstraintViolationException: Password violates password constraint (^(?=.*\d).{7,9}$).
at org.apache.jackrabbit.oak.spi.security.user.action.PasswordValidationAction.validatePassword(PasswordValidationAction.java:105)
at org.apache.jackrabbit.oak.spi.security.user.action.PasswordValidationAction.onPasswordChange(PasswordValidationAction.java:76)
at org.apache.jackrabbit.oak.security.user.UserManagerImpl.onPasswordChange(UserManagerImpl.java:308)
To learn about AEM Screens Player, see Working with Screens Player.
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.