Content Comparison

...

...

Accounts managed in CAMIS:

There are three types of accounts that are managed VIA the Admin section of the left-hand menu in CAMIS:

...

• Administrative (2FA) 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

• Create 2FA admin account for CAMIS
  

• 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 (from development databases):
      

      

  • 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
    

    

...

• Manages account access to CAMIS and eMER.
  

• CAMIS User records, are manually added per Create 2FA admin account for CAMIS

• They have the STAKEHOLDER_ID as the records in AC040_STAKEHOLDER and AC043_INTERNAL_STAKEHOLDER.
  

• The CAME and CAME Associate records (eMER access) are automatically created.

• They have the same STAKEHOLDER_ID as the records in AC040_STAKEHOLDER and AC044_EXTERNAL_STAKEHOLDER.
  

...