• Replies 2 replies
  • Subscribers 1 subscriber
  • Views 19 views
  • Users 0 members are here
Options
Related

ThinClient Access UserBased Security

Admin
Hi there,

Requirement:
ThinClient1 : can access page1,2,3
ThinClient2 : can acess page 4,5,6

Is it possible to specify accessible screens based on their username for thinclient?

I checked; and there is no screen distribution for the security.

Do I need to insert an interlock to buttons to disable based on `UserName` tag?

Many thanks
Parents
  • You can specify a security level for every Command (i.e. button) and you can specify a security level for every Screen. There is only one setting (Security), and it specifies the level needed to access the item. You would have to assign each of the users to a different group. If you gave ThinClient1(group) the Runtime Security Level 11 to 11, and gave ThinClient2(group) the Runtime Security Level 12 to 12, then you could set the Security to 11 for all items that ThinClient1 has access to and set the Security to 12 for all items that ThinClient2 has access to.

    For Commands (i.e. buttons) the text on the button will be greyed out and the button will not work unless the proper security level is used. For screens, you will receive a dialog box informing the user that they do not have access to that screen when they attempt to access it.

    If you have items that both users need to access, then you could give ThinClient1 Runtime Security Level 10 to 11 and give ThinClient2 Runtime Security Level 11 to 12. Then set Security to 10 for items accessible only to ThinClient1, set Security to 12 for items accessible only to ThinClient2 and set Security to 11 for items that both users need access to.

    If you have more than 2 groups, then things get more complicated and you would have to do the enabling yourself (not using the Security setting). You could give each group its own Security Level (like in first example) then use the Disable field of the Command with something like NOT(GroupHiLevel=11 OR GroupHiLevel=12 OR GroupHiLevel=13 OR GroupHiLevel>99) This would enable the item for groups 11, 12 and 13 and any group with a Security High Level greater than 99.
Reply
  • You can specify a security level for every Command (i.e. button) and you can specify a security level for every Screen. There is only one setting (Security), and it specifies the level needed to access the item. You would have to assign each of the users to a different group. If you gave ThinClient1(group) the Runtime Security Level 11 to 11, and gave ThinClient2(group) the Runtime Security Level 12 to 12, then you could set the Security to 11 for all items that ThinClient1 has access to and set the Security to 12 for all items that ThinClient2 has access to.

    For Commands (i.e. buttons) the text on the button will be greyed out and the button will not work unless the proper security level is used. For screens, you will receive a dialog box informing the user that they do not have access to that screen when they attempt to access it.

    If you have items that both users need to access, then you could give ThinClient1 Runtime Security Level 10 to 11 and give ThinClient2 Runtime Security Level 11 to 12. Then set Security to 10 for items accessible only to ThinClient1, set Security to 12 for items accessible only to ThinClient2 and set Security to 11 for items that both users need access to.

    If you have more than 2 groups, then things get more complicated and you would have to do the enabling yourself (not using the Security setting). You could give each group its own Security Level (like in first example) then use the Disable field of the Command with something like NOT(GroupHiLevel=11 OR GroupHiLevel=12 OR GroupHiLevel=13 OR GroupHiLevel>99) This would enable the item for groups 11, 12 and 13 and any group with a Security High Level greater than 99.
Children
No Data