Doubts about security

0
I have an application-level role name'Module_X_Admin' and a module nameX that has the same role at the module level. Doing this results in the error: "No access to nanoflow "Mobile.DS_AccountHome' for user role 'Module_X_Admin' (with no roles defined in module "Mobile")." But the role doesn't actually exist in the mobile module, because I don't use anything from that module. DS_AccountHome is only called in the mobile module and nowhere else. Why does this happen?
asked
1 answers
0

Short answer: name matching does not create access.

In Mendix, project user roles (e.g., Module_X_Admin) must be mapped to module roles per module. Your user role is not mapped to any role in the Mobile module. Somewhere your app lets that user role reach an entry point that calls Mobile.DS_AccountHome (most commonly the Native Mobile navigation profile Home nanoflow). During consistency checks, Studio Pro verifies access for every user role that can reach that navigation/profile, and it flags:No access to nanoflow 'Mobile.DS_AccountHome' for user role 'Module_X_Admin' (with no roles defined in module 'Mobile').

Why it happens even if you “don’t use” the module: the navigation/profile or a page/action accessible to Module_X_Admin references that nanoflow, so access must be granted or the reference removed.

Fix options (pick one):

  1. Map Module_X_Admin to a Mobile module role and grant that role access to DS_AccountHome.

  2. Restrict the Native Mobile navigation profile to only the user roles that actually use mobile (uncheck Module_X_Admin).

  3. Move DS_AccountHome out of the Mobile module (to a module the role is mapped to), or remove the reference.

  4. If you truly don’t use Mobile at all, disable/delete the Native Mobile navigation profile and any links to Mobile nanoflows/pages.

Checklist to locate the reference quickly:

  • Project > Navigation > Native mobile profile: check Home page/nanoflow and role visibility.

  • Search usages of DS_AccountHome to see if any page/microflow button reachable by Module_X_Admin triggers it.

  • Project Security > User roles > Module_X_Admin: confirm no Mobile module roles are mapped.

answered