Hi Martene, log to the NWA, select Configuration, then Authentication and Single Sign-On. Select "SAP-J2EE-Engine" Policy configuration and in details there are Login Modules with Move Up and Down buttons. In my case moving "
com.sap.engine.services.security.server.jaas.ClientCertLoginModule" to bottom solved the issue.
Hi Yogesh and Michal, I have now the same problem as you both.
* Yogesh, I tried your solution, but it does not work in my case.
* Michal, could you please explain what I have to do exactly to move the login module com.sap.engine.services.security.server.jaas.ClientCertLoginModule down in list in NWA? I do not understand what to do exactly.
Thanks a lot, MK
Hello Michal,
We have same issue with our one of the solution manager and we have HIGH priority message open with SAP but they are not able to find solution for this issue from last 2 months.
Good luck.. Look at attachment
I will keep you posted if I find solution from them
Cheers,
Yogesh
Hello,
I solved the issue myself :
problem was solved by moving login module com.sap.engine.services.security.server.jaas.ClientCertLoginModule down in list in NWA (setting lower priority). I suppose, that this module is responsible for creating virtual user "hostname.domain.local", which have not required authorizations for the operation. After that, correct user SM_ADMIN_BSM is used and everything is working as expected.
Hello,
This is also one of the solution...
Open the NetWeaver Administrator
Go to tab ‘Configuration’ and select ‘Identity Management’
Select ‘Groups’ as Search Criteria and enter ‘SAP_RCA_AGT_CONN’ as group name
Press ‘Go’
Select the now displayed group
Go to tab ‘Assign Roles’ and press ‘Modify’
Search for ‘Administrator’
Select the role and press ‘Add’
Press ‘Save’
Now you can execute the SSO configuration step.
One more SAP note :
2400079 - Byte Code Adapter Installation ends in error: "Failed to connect via p4 channel - com.sap.smdagent.vmmanager.VMManagerException: Failed to use JMX service
-Yogesh
Hi Michal,
You can easy overcome this issue by simply adding the role SAP_J2EE_ADMIN to the user account created for the SPML service execution.
The user account credentials are input during step 4 of the Managed System Configuration Solution Manager wizard.
Take a look at SAP notes, for a better alternative:
Add comment