Configure Galaxy security
- Last UpdatedJul 17, 2024
- 1 minute read
Galaxy security uses the local Galaxy configuration to authenticate users. All security for the Galaxy is specified and contained at the specific Galaxy level. When the user logs on, security credentials are checked and access to areas and activities is granted at the Galaxy level.
Regardless of the security system, a single user can have multiple accounts. For example, a user can have an account that provides permissions for working with instances but not templates. The same person can have another supervisory account for working with templates and managing users in the ArchestrA environment.
Each account requires a different user name and password. For example:
|
User Name |
Password |
Access |
|---|---|---|
|
bsmith |
password |
Instances, not templates |
|
bobsmith |
super |
Instances, templates, not managing users |
|
Robertsmith |
admin |
Instances, templates, managing users |
After you change security for a Galaxy, you see the following behaviors and conditions:
-
When you change the authentication mode security, the IDE restarts.
-
To switch users, the person must log on as the new user by clicking Change User on the Galaxy menu.
-
If you previously configured security under one authentication mode and then switch authentication modes, only those users created while configuring the new mode are available. Other users are not deleted, just unavailable in the new mode.
-
Objects that are reassigned to different security groups are marked as "pending update" and require redeployment for the change in security group to take effect.
-
If security was previously configured for an OS-based authentication mode, reconfiguring security synchronizes the user’s full name and OS groups if some data in the OS has changed.