Security in Multiple Tablespaces (Oracle)

If you are using security on multiple tablespaces, you maintain your afm_users and afm_groups information in the default tablespace associated with the AFM_SECURE user. Even if your project resides in another tablespace, the program will find the security tables.

To see how this works, suppose you invoke the Set Security On task and use Open Project to log into the account "HCN" with password "HCN."

When Archibus opens an Oracle project, it first connects to Oracle using the AFM_SECURE account and password. It logs into the default tablespace for AFM_SECURE, which in the example above is the AFM_P1 tablespace. Archibus verifies the user login information against the afm_users and the afm_groups tables in the AFM_P1 tablespace.

The program then logs into the database again as "HCN." Since the default tablespace is HCN_P1, the Archibus program looks for the data tables of the project (bl, fl, etc.) in the HCN_P1 tablespace.

Note: The scenario above suggests you must configure one security account for each user or group, for access to all projects. A single security account might be a sensible configuration for some cases, but it is not always desirable, nor is it a requirement. You can configure multiple security logins, one for each project.