cancel
Showing results for 
Search instead for 
Did you mean: 

Authorization check for caller assignment to J2EE security role

former_member4958
Participant
0 Kudos

Dears experts, in the default.trc logs in, my Enterprise Portal NW2004s, appear this error:

#1.#0018714E4A14005E000027E1000057B8000441BB7EF2FC03#1198173451524#com.sap.engine.services.security.roles.SecurityRoleReference#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleReference#Guest#2126####46ce8210aefd11dcc68f0018714e4a14#Thread[Thread-59,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Security/Audit/J2EE#Java###: Authorization check for caller assignment to J2EE security role [ : ] referencing J2EE security role [ : ].#5#ACCESS.ERROR#service.jms.default.authorization#administrators#SAP-J2EE-Engine#administrators# #1.#0018714E4A14005E000027E5000057B8000441BB7F8BDC21#1198173461543#com.sap.engine.services.security.roles.SecurityRoleImpl#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#Guest#2127####46ce8210aefd11dcc68f0018714e4a14#Thread[Thread-59,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Security/Audit/J2EE#Java###: Authorization check for caller assignment to J2EE security role [ :

Any idea about it?

Thanks friends

Accepted Solutions (1)

Accepted Solutions (1)

former_member4958
Participant
0 Kudos

We are in the SP13 to

Former Member
0 Kudos

Hi,

on which patch level are you? I think you can ignore this error. These messages should have been removed with SAP J2EE ENGINE CORE Sp13 patch 3 (but I haven't checked this yet)

If they are bothering you, you should be able to "hide" these messages by setting /System/Security/Audit to "none".

Regards,

Holger.

benjamin_houttuin
Active Contributor
0 Kudos

Hi Holger,

Thanks for the tip, it could be the case, I just checked and we are on Patch 0 for JEECOR as you can see here below:

sap.com/SAP-JEECOR 7.00 SP13 (1000.7.00.13.0.20070907082334) 20071028144036

sap.com/SAP-JEE 7.00 SP13 (1000.7.00.13.2.20071026143730) 20071203150628

Will inform some people internally to patch to atleast 3 to check if it still occures.

Anyway, Thanks again..

Benjamin Houttuin

Former Member
0 Kudos

Are there any official OSS notes on this issue?

Did patching to 3 fix the error?

Regards

Craig

Answers (3)

Answers (3)

Former Member
0 Kudos

Please see the following link.

This resolved the issue for me:

http://www.sapfans.com/forums/viewtopic.php?p=927870&sid=9dade8656a8fd2101bbb9883cbfb167e

former_member4958
Participant
0 Kudos

Dear Experts, I don't apply the patch number three yet.

Former Member
0 Kudos

hi All

i am also getting same kind of Error Message.

i am aslo using NW04s SP13 patch 0. could you suggest me that needful??

thanks

narpal

benjamin_houttuin
Active Contributor
0 Kudos

We have it to and we are on NW2004S SP13...

Does someone in the SDN community have a clue?

Thanks in Advance,

Benjamin Houttuin

Edited by: Benjamin Houttuin on Dec 20, 2007 8:44 PM