Hi,
I am getting Tons of error logs "Registered role required "??, each and every screen I have set as registered.?
After login is it required to check roles once calling server actions/screen.
I am calling the data and accessing screens from different different application and module for same user ?
Registered role requiredat _Controller.CheckPermissions(HeContext heContext)at ssABCOnline.ScreenServices.SimplifyOnline_MainFlow_XYZ_Controller.<ScreenDataSetGetType>b__2d(HeContext heContext, String screenName, JObject screenModel, JObject inputParameters, JObject clientVariables) at OutSystems.RESTService.Controllers.ScreenServicesApiController.endpoint(String input, String endpointName, String apiVersion, EndpointImplementationDelegate implementation)
Please help me to avoid these logs from service center as its huge..also tell me root cause why its happening as after login it should not required to check the role permissions again?????
This warning is generated when an anonymous user is trying to access a screen where the screen roles are set to registered. Outsystems will redirect the user to the login page, but still logs this warning.
Bas de Jong wrote:
Hi Bas De Jong, thanks for quick reply.
we are getting these logs post login when I am navigating between screens and module.I am not redirecting to Login until i clicked on logout.. Post login it should not required to check permission as all screens are registered and I am a registered use. Please help
Hi Dileep,
In my past experience working with one of the mobile application project, I also evidenced the same bunch of error Logs in the service center error Log section. I tried my best to trace out the root cause but I was unable to make it...
Confusion: Even though the user gets successfully logged-In to the application, still it throws the error "Registered role required". In general, it is stated that if the user is a valid user i.e. Registered User within the application env - he/she does assigned with OS Default Registered Role.
Observation: In my experience, the above stated error is enrolled whenever a server action is invoked/called...
Solution:
1) Create an additional Application Role
2) After every successful User login - Explicitly Assign/Grant the logged-in user with the defined Role (point-1) using Grant<RoleName>Role Server Action node
3) In the Error Log, Observe that in which ever Server action the error is getting logged, in all those Server action logic flow introduce this particular Grant<RoleName>Role Server Action node
I think point 3 is not that much required, without that also it will work...
Hope this helps you!
Regards,
Benjith Sam
I know this is an older post, but as I had the same problem, I figured I might as well post my solution here for anyone else with this problem. What fixed it for me, was just re-assigning the group role in the OutSystems Users application to the application specific role. Nothing had changed, but re-assigning seemed to work.
Kind regards,
Chris
This new implementation might help:https://success.outsystems.com/documentation/11/setup_and_maintain_your_outsystems_infrastructure/setting_up_outsystems/disable_registered_role_required_error_logs/