Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

Status Future consideration
Workspace Jedox Platform
Categories Other
Created by Guest
Created on Jul 13, 2020

Disable activation of users in Jedox while SSO is used

Normally, Whether SSO is enabled or not,it is possible to activate/deactivate users in Jedox at "Administration" > "Users" or by entering "1" in "inactive" column in the relevant system cubes.

But, When SSO is enabled, it may cause end-users to wrongly change its flag and consequently unexpected /unwanted behavior may occur.

Thus , we would like you to gray out the user panel (or at least "Activate" checkbox there ) and lock the cells of "inactive" column in the relevant system cubes when Jedox installation is configured to use SSO.

  • Guest
    Reply
    |
    Aug 3, 2020

    Hi, Thank you for your comment.

    Please kindly see the following for the detailed description of our idea:

    ・Our request is to change the current behavior that there is no access restriction to user properties(especially "inactive" flag) while Jedox is configured to use SSO authorization.

    ・Our customer has encountered the unexpected behavior after they changed user active status in Jedox while SSO is used, which are that error message popped up when they tried to open Integrator panel (see the image"error_1") and tried to execute ETL from a php macro(see the image"error_2").

    As we were told that user active/inactive status are all controlled by AD while SSO authorization is used ,we are afraid that some customers may wrongly change the status in Jedox because it is still changeable.

    Thus, we request that access to user properties("inactive"property) be restricted such as by graying out the checkbox of "Active" (See image"image1") and by rocking cells of "inactive"(See image"image2") while SSO authorization is used.

    If there are still something unclear , please kindly let me know.

  • Guest
    Reply
    |
    Jul 24, 2020

    Hi, can you please clarify your Idea to help us understand the request better? What behaviour exactly is unexpected?