Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM Screens Player fails to generate token

Avatar

Avatar
Validate 25
Level 4
Karl515
Level 4

Likes

14 likes

Total Posts

157 posts

Correct Reply

11 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile

Avatar
Validate 25
Level 4
Karl515
Level 4

Likes

14 likes

Total Posts

157 posts

Correct Reply

11 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile
Karl515
Level 4

24-06-2019

Hello,

We installed the most compatible AEM Screens Player version to the server's version (that is 6.4.2), Then configured the player to connect to the server. But the player fails to generate token, with the status under System Information "initial (link-up) (unauthenticated)".

Moreover, we have followed server configuration in https://helpx.adobe.com/experience-manager/6-4/screens/using/configuring-screens-introduction.html. rough summary:

   * Allow Empty Referrer Requests

   * Enable Touch UI for AEM Screens

   * AEM in NOSAMPLECONTENT runmode

   * Password Restriction

1778370_pastedImage_0.png

1778371_pastedImage_1.png

We've also tried /system/console/configMgr/org.apache.jackrabbit.oak.spi.security.user.action.DefaultAuthorizableActionProvider yet still to no good.

What could be the issue?

Thanks

Replies

Avatar

Avatar
Boost 5
Employee
tanyakapila
Employee

Likes

9 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Applaud 5
Affirm 3
View profile

Avatar
Boost 5
Employee
tanyakapila
Employee

Likes

9 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Applaud 5
Affirm 3
View profile
tanyakapila
Employee

25-06-2019

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. I request you to try removing any password restriction at

system/console/configMgr/org.apache.jackrabbit.oak.spi.security.user.action.DefaultAuthorizableActio...

Avatar

Avatar
Validate 25
Level 4
Karl515
Level 4

Likes

14 likes

Total Posts

157 posts

Correct Reply

11 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile

Avatar
Validate 25
Level 4
Karl515
Level 4

Likes

14 likes

Total Posts

157 posts

Correct Reply

11 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile
Karl515
Level 4

25-06-2019

Hi.

Yup it was removed. That's why I've stated it in my question. But still no good.

Thanks.

what else could have cause the error?

Avatar

Avatar
Give Back
Level 1
sukritikohli
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Give Back
View profile

Avatar
Give Back
Level 1
sukritikohli
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Give Back
View profile
sukritikohli
Level 1

14-07-2019

Did you get any solution for this?
I am facing the same issue