cancel
Showing results for 
Search instead for 
Did you mean: 

Logon via EAM_Launchpad fails and locks the FF_ID

Former Member
0 Kudos

Dear GRC Team,

I am currently configurating GRC AC 10.0 SP16 for our company as a demo system.

I have the following scenario:

- The GRC system is also the Target system.

- We are using Centralized FF.

- We are using ID based FF.

All steps necessary have been performed. (role assignments, parameter settings, sync jobs, etc.)

When executing transaction GRAC_EAM I can see the FF_ID assigned to my user.

Also I am able to choose the ID.

The usual pop-up box will appear asking me for reason code and so on.

When hitting enter or execute I receive that the loggon attempt failed and after repeating this of course the ID will be logged.

Does anybody have an Idea?

Kind regards in advance

Amir

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member226273
Active Participant
0 Kudos

Hello Amir,

Have you checked for RFC related authorization for both FF id and firefighter?

Please check if any authorization check is getting failed for FF id and firefighter.

Kind regards,

Yashasvi

0 Kudos

Hello Amir,

Try to set a initial password for the FF, if you are using CUA set the initial password in CUA master,

Regards,

Rafael Guimbala

Former Member
0 Kudos

Hi,

I guess you mean the FF_ID... it has initial PW set via CUA

former_member197694
Active Contributor
0 Kudos

Hello,

check below authorization

1. Assign S_ICF and S_RFCADM authorization objects to the Firefighter.

2. Assign S_RFCACL authorization object to the Firefighter ID.

also refer below NOTE

2035815 - Firefighter ID (FFID) is shown locked in EAM launchpad, even though no firefighter user is...

Regards

Baithi

chandani_kaur
Active Participant
0 Kudos

Hello Amir,

Kindly check if the RFC user is having password change authorization. Also check St22 for any authorization related dump in plugin system.

Thanks & Regards,
Chandani Kaur

Former Member
0 Kudos

Hi,

Have you ensured the FFID has been set up as a Service user type? Also ensure the user exit has been deployed om the GRC system itself.

Former Member
0 Kudos

Hi,

Yes they are from Type Service User.