few doubts in FF & AE

[Former Member]

Hi all,

Your inputs are required on the following:

We are in the process of implementation of AE and FF. Can any body tell me which is the best practice for implementing FF (role based approach or FF ID based approach)

Is auto provisioning of FF ID is possible through AE 5.2. If not is there is customization which helps to auto provision the FF ID's

Whether 5.3AE supports autoprovisioning. Does 5.3 version of FF also suports both the approaches.

Regards,

Ranjit

[koehntopp]

Hi,

- My suggestion is usually the ID based aproach, as it allows for better control and visibility to the user (they have to document why they want to use it, so they become aware this is something special)

- AE 5.2 can not directly provision FF IDs. You can, however, create a path that ends with the FF administrator as the final approver, who will then do that manually. At least you'll have approval and audit trail.

- AE 5.3 (a.k.a. CUP) will allow to directly provision FF IDs

Frank.

[Former Member]

Fully Agree with Frank's answer.

In second point as he said, can not directly provision, that technically means Access Enforcer is not integrated with virsa tool /n/virsa/vfat as it is required to assign a firefighter ID to a user and have to maintain a user in Firefighter Table. This feature is not available in AC 5.2 but in 5.3 positively.

however you can provision respective roles to Firefighters, Owners and Controllers through workflow process and finally a security administrator can manually add these users to Firefighter tables through virsa tool /n/virsa/vfat.

Best Regards,

Amol Bharti