Skip to main content
InSource Solutions

TN - 1320 One or more users are able to log on to an application using OS Group Based Security but are not granted permissions

  1. Last updated
  2. Save as PDF

Description

 

This article from InSource shows how to resolve situations where one or more users are able to log on to an application using OS Group Based Security but are not granted permissions.

  • Author: Peter Farrell
  • Published: 12/21/2022
  • Applies to: Application Server all versions upto 2020

Details

One or more specific users log on to an application but are not granted permissions where the Galaxy is configured for OS Group security. All other users with the same group membership and correct permissions options selected within Galaxy OS Group Based/Users security are able to log on and are granted permissions.

Open the System Management Console > Platform Manager and confirm that the Galaxy Repository platform is on scan. If it is off scan, you should right click and place the platform back on scan. You may also have to select each engine under the Galaxy Repository platform and place them back on scan.

82687_000.png

With the Galaxy Repository platform off scan, a file named data2.txt, which holds security related data and existing on both the Galaxy Repository and remote platform, would not have been updated on the local platform where the users were logged on or on the Galaxy Repository resulting on the users not being granted permissions.

After placing the GR back on scan, and redeploying the platform, the data2.txt files should match time and dates stamps and users should be able to log in and gain permissions.

You may also need to open the IDE and navigate to Galaxy > Configure > Security where the system with automatically synchronize the OS users to the Galaxy.

82687_001.png