Accounts managed in CAMIS:
There are three types of accounts that are managed VIA the Admin section of the left-hand menu in CAMIS:
CAME Admin
CAME Associate Admin
CAME User
CAMIS User:
Refers to an account for logging into the CAMIS application.
CAMIS User account are added / administered via the User Admin menu item.
For the majority of users logging into CAMIS the roles are defined in the “Role section of the profile and nothing further needs to be done.
There are no corresponding records in the 2FA database for regular CAMIS Users.
These users CANNOT update CAME or CAME Admin accounts.
Administrative privileges are manually added to some CAMIS User accounts on, a limited basis for users, such as developers and the business, authorized to
add/update/maintain CAME/CAME Associate accounts
The main 2FA tables are:
AC040_STAKEHOLDER:Main table for managing user accounts for accessing CAMIS and eMER.
Accounts with access to CAMIS are identified by STAKEHOLDER_TYPE_CD = 1
Accounts with access to eMER are identified by STAKEHOLDER_TYPE_CD = 2
In some cases, if a user has access to CAMIS and eMER they will have two records in AC040_STAKEHOLDER:
One for their CAMIS User account (STAKEHOLDER_TYPE_CD = 1)
The other for their eMER account STAKEHOLDER_TYPE_CD = 2).
Example:
In order for the account to work properly the following has to be TRUE:
TWOFA.AC040_STAKEHOLDER.GLOBAL_USERID_LBL for account with STAKEHOLDER_TYPE_CD = 1
is identical to
CAMIS.AA008_APPLICATION_USER.TWOFA_USERID_LBL identified by the user’s TC_USER_ID
The update has to be performed manually.
Once a value is set for TWOFA.AC040_STAKEHOLDER.GLOBAL_USERID_LBL and / or CAMIS.AA008_APPLICATION_USER.TWOFA_USERID_LBL the value(s) can only be changed by temporarily disabling the trigger, making the change(s) and then re-enabling the trigger.developers are permitted to disable/re-enable the trigger on development. On acceptance and production this can only be done by a corporate DBA. In a case where we needed this done on acceptance for CAMIS and 2FAa, after a refresh, the dev team provided the script to the DBAs.
Example: TWOFA.AC040_STAKEHOLDER.GLOBAL_USERID_LBL and CAMIS.AA008_APPLICATION_USER.TWOFA_USERID_LBL are identical in the images below.
TWOFA.AC040.STAKEHOLDER
CAMIS.AA008_APPLICATION_USER
AC043_INTERNAL_STAKEHOLDER
Per the table name, AC043_INTERNAL_STAKEHOLDER contains ONE manually created record with the same STAKEHOLDER_ID as in AC040_STAKEHOLDER
AC040_STAKEHOLDER where STAKEHOLDER_TYPE_CD = 1There should NOT be any records corresponding with
AC040.STAKEHOLDER.STAKEHOLDER_TYPE_CD = 2
Example:
Parent record with STAKEHOLDER_TYPE _CD =1 in AC040_STAKEHOLDER:
Corresponding record in AC043_INTERNAL_STAKEHOLDER
AC044_EXTERNAL_STAKEHOLDER
Per the table name, AC044_EXTERNAL_STAKEHOLDER contains ONE record, which is automatically generated by CAMIS once the “eMER profile” section of a CAME or CAME Associate account is completed. with the same STAKEHOLDER_ID as in AC040_STAKEHOLDER
AC040_STAKEHOLDER where STAKEHOLDER_TYPE_CD = 1.There should NOT be any records corresponding with AC040.STAKEHOLDER.STAKEHOLDER_TYPE_CD = 1
Example:
Parent record with STAKEHOLDER_TYPE _CD =1 in AC040_STAKEHOLDER:
Corresponding record in AC044_EXTERNAL_STAKEHOLDER
AC002_XREF_APPLICATION_USER
Manages account access to CAMIS and eMER.
The eMER record is automatically created.
The CAMIS record has to be added manually and as per the instructions
(Create 2FA admin account for CAMIS )
CAME account
CAME = Civil Aviation Medical Examiner (doctors).
For access to eMER.
These accounts can only be updated by a user with a CAMIS account with 2FA privileges.
a the CAMIS account without 2FA administrative will not be able to activate or regenerate activation codes for eMER accounts.
CAME accounts are in CAMIS via the CAME Admin menu item (under Admin)
In development and acceptance these accounts are created by a developer.
in prod the accounts have to be created by a business client with a CAMIS account having 2FA privileges.
Developer accounts cannot appear in the existing CAME drop-down. We have a process for adding developer accounts that are able to login to eMER on Prod for read-only purposes. These accounts are not currently able to add data to eMER as there are no corresponding records in the CAMIS database..
CAME Associate account
CAME Associates
For access to eMER.
These accounts can only be updated by a user with a CAMIS account with 2FA privileges.
a the CAMIS account without 2FA administrative will not be able to activate or regenerate activation codes for eMER accounts.
CAME accounts are in CAMIS via the CAME Admin menu item (under Admin)
In development and acceptance these accounts are created by a developer.
in prod the accounts have to be created by a business client with a CAMIS account having 2FA privileges.
Developer accounts cannot appear in the existing CAME Associate drop-down. We do not have a process for adding developer CAME Associate accounts on prod.
0 Comments