WASUSERNAME header not found or empty Aborting

[Former Member]

Hi All

finding the below entries in the default.trace

1.5^H#721C7EF26C02007C00000577015F009A00050C0EA23DEE8A#1420631874596#com.netegrity.siteminder.sap.webas.jaas.SiteMinderLoginModule#sap.com/tc~wd~dispwda#com.netegrity.

siteminder.sap.webas.jaas.SiteMinderLoginModule.handleSSOCallBacks()#Guest#0##69EC5770966411E4CAA300000083D826#69ec5770966411e4caa300000083d826-0#69ec5770966411e4caa300

000083d826#SAPEngine_Application_Thread[impl:3]_13##0#0#Error#1#/System/Security#Plain###WASUSERNAME header not found or empty - Aborting...#

ours is a portal system , with siteminder configured ,

few of the customers facing the irj/portal is taking more time to them to respond.

is above like errors , affect that particular users ?  from our side when we check ,we are getting normal response

meanwhile , where to search of the above errors of siteminder related in sdn forum

Thanks in advance

[Former Member]

Team, what was the solution,. even we are facing similar technical issue in our landscape WECM portal Appln

[Former Member]

Hi Jinesh

you are correct , sap also suggested the http trace from customer end.

what is the error  WASUSERNAME header not found or empty appearing for siteminder

Hi Divyanshu - all the parameters mentioned by your are normal

Thanks in advance

Regards

[jinesh_jayan]

Hi Sidharth,

Use httpwatch in the end user  system  to find out  which path is taking long time in the total login time.

Also take the trace from IE and Firefox/Chrome ,if possible

Hope This Helps,

[divyanshu_srivastava3]

Hi Sid,

I am not sure what is happening in your system, however, the 1st few things that I would like you check is the CPU utilization for server nodes, GC on server nodes and thread dump of all server nodes.

Do above check, and if it's not something complex, you will get the root cause.

Meanwhile, alos use HTTP watcher/tracer and Wily to dig in more.

Regards,