Skip to main content
Solved

How to fix error: USER doesn't have READ permission on the engine which appears in sdc.log

  • May 25, 2022
  • 1 reply
  • 268 views

Pradeep
StreamSets Employee
Forum|alt.badge.img+1
  • StreamSets Employee
  • 48 replies

Symptoms of the issue described as below.

  1. When trying to access listed data collector(s) in page Administration > Data Collectors it redirects to the control hub login page and sdc.log shows the below.

2022-05-23 10:29:08,574 [user:] [pipeline:] [runner:] [thread:webserver-48607] [stage:] ERROR AbstractSSOService - Exception while doing remote validation for token 'TOKEN:00a623cd-fe81-45...' component '-':  Could not connect to security service: com.streamsets.lib.security.http.ForbiddenException: ISSUES=code=DPM_02, message=User validation failed
2022-05-23 10:29:09,387 [user:] [pipeline:] [runner:] [thread:webserver-48530] [stage:] WARN RemoteSSOService - Could not do User session validation, going inactive: com.streamsets.lib.security.http.ForbiddenException: ISSUES=code=DPM_04, message=USER doesn't have READ permission on the engine
2022-05-23 10:29:09,387 [user:] [pipeline:] [runner:] [thread:webserver-48530] [stage:] ERROR AbstractSSOService - Exception while doing remote validation for token 'TOKEN:aee0cea2-ad48-48...' component '-': Could not connect to security service: com.streamsets.lib.security.http.ForbiddenException: ISSUES=code=DPM_04, message=USER doesn't have READ permission on the engine

  1. job/pipeline runs fail with the similar in (1).

Best answer by Pradeep

This is likely caused due to permission(share) settings for the user who is accessing the data collector. You can go to Execute > Data Collectors > Select data collector > Share on control hub(SCH), verify the share permissions and update the access to the concerned user as needed.

View original
Did this topic help you find an answer to your question?

1 reply

Pradeep
StreamSets Employee
Forum|alt.badge.img+1
  • Author
  • StreamSets Employee
  • 48 replies
  • Answer
  • May 25, 2022

This is likely caused due to permission(share) settings for the user who is accessing the data collector. You can go to Execute > Data Collectors > Select data collector > Share on control hub(SCH), verify the share permissions and update the access to the concerned user as needed.


Reply