Created on 12-05-2019 11:45 PM - last edited on 12-11-2019 03:00 PM by lwang
Hi All,
using CDH 5.15.1
security : kerberos enabled
whenever i clicked on oozie workflow under my documents getting error 403 forbidden
i want to edit oozie workflow
Created 03-26-2020 11:54 AM
Hi @syedshakir ,
Thanks for your update. Could you please clarify if you are talking about a new issue here? The original issue is not able to access oozie workflow from my documents and got 402 error message. And the latest update you mentioned about users not able to kill jobs.
If the original issue got resolved, please close this thread and I would suggest you opening a new thread to explain what is the new issue and give some error message and screenshots will help.
Thanks,
Li
Li Wang, Technical Solution Manager
Created 12-08-2019 03:44 AM
@syedshakir There are 2 permissions required for Dashboard access:
search.access
dashboard.access.
Please goto Hue > User profile > Groups > and then grant the access on above options for user. Logout and log back In. Le me know if issue persist.
Created 12-08-2019 04:01 AM
Hi ,
dashboard.access is already given but search.access is not visible on screen attached screenshot
Created 12-13-2019 10:21 AM
Hi @syedshakir ,
Please give oozie.access to the user and then try it again.
Thanks,
Li
Li Wang, Technical Solution Manager
Created 02-21-2020 02:40 AM
Hi Wang ,
i did not find any option like oozie.access , or
provide the step by step process.
thanks,
syed
Created 02-21-2020 01:24 PM
Hi @syedshakir,
Can you please try steps below?
Thanks and hope this helps!
Li Wang, Technical Solution Manager
Created 03-26-2020 07:13 AM
i have tick mark the three option to the particular, still issue persist,
user unable to kill jobs
Created 03-26-2020 11:54 AM
Hi @syedshakir ,
Thanks for your update. Could you please clarify if you are talking about a new issue here? The original issue is not able to access oozie workflow from my documents and got 402 error message. And the latest update you mentioned about users not able to kill jobs.
If the original issue got resolved, please close this thread and I would suggest you opening a new thread to explain what is the new issue and give some error message and screenshots will help.
Thanks,
Li
Li Wang, Technical Solution Manager