Receive request attribute n in CA SiteMinder Policy Trace logs

I had recently opened a case regarding 'missing' codes that are part of the SiteMinder API that were not documented. Thanks to CA's Technical Support, I'm able to share them with you. Trace LogsHopefully this will be useful when trying to look at SiteMinder Policy Server trace logs and figure out which API event is being called. The messages in question are the "Receive request attribute n, data size is m" messages in SmMessage.cpp which is part of the trace logging for login/logout authorization. The attribute IDs in question are the SmAgentTli_Attr_t numbers which are part of the SmAgentTli_ReqAttr_t structure. So, for example, attribute 204 is SmAgentTli_RealmOid

  • SmAgentTli_AuthSecurityContext = 138
  • SmAgentTli_AuthDomainName = 139
  • SmAgentTli_SessionVarName = 140
  • SmAgentTli_SessionVarData = 141
  • SmAgentTli_SessionVarFlags = 142
  • SmAgentTli_ConfigType = 143
  • SmAgentTli_ConfigData = 144
  • SmAgentTli_MonitoringData = 145
  • SmAgentTli_VarsToBeResolved = 146
  • SmAgentTli_VarsResolved = 147
  • SmAgentTli_ManagementCommand = 148
  • SmAgentTli_ManagementData = 149
  • SmAgentTli_DomainOid = 150
  • SmAgentTli_AuthDirOid = 151
  • SmAgentTli_UserUniversalId = 152
  • SmAgentTli_CurrentServerTime = 153
  • SmAgentTli_StartSessionTime = 154
  • SmAgentTli_LastSessionTime = 155
  • SmAgentTli_IdentitySpec = 156
  • SmAgentTli_UpdateAttrOid = 157
  • SmAgentTli_StatusMsg = 158
  • SmAgentTli_AgentTimestamp = 159
  • SmAgentTli_V3TTL = 160
  • SmAgentTli_ServiceLibrary = 161
  • SmAgentTli_ServiceFunction = 162
  • SmAgentTli_ServiceParameter = 163
  • SmAgentTli_ServiceData = 164
  • SmAgentTli_AgentTimezone = 165
  • SmAgentTli_AgentCipherStrength = 166
  • SmAgentTli_SessionDrift = 167
  • SmAgentTli_BufferLimit = 168

// DoManagement attributes returned by the server to the agent

  • SmAgentTli_Management_ConfigUpdate = 188
  • SmAgentTli_Management_AffiliateKeyUpdate = 189
  • SmAgentTli_Management_AgentKeyUpdate_Next = 190
  • SmAgentTli_Management_AgentKeyUpdate_Last = 191
  • SmAgentTli_Management_AgentKeyUpdate_Current = 192
  • SmAgentTli_Management_AgentKeyUpdate_Persistent = 193
  • SmAgentTli_Management_FlushAll = 194
  • SmAgentTli_Management_FlushAllUsers = 195
  • SmAgentTli_Management_FlushThisUser = 196
  • SmAgentTli_Management_FlushAllRealms = 197
  • SmAgentTli_Management_FlushThisRealm = 198

// Agent API - Server protocol attributes (all strings)

  • SmAgentTli_ManagementTimestamp = 199
  • SmAgentTli_DeviceName = 200
  • SmAgentTli_Resource = 201
  • SmAgentTli_Action = 202
  • SmAgentTli_RealmName = 203
  • SmAgentTli_RealmOid = 204
  • SmAgentTli_SessionId = 205
  • SmAgentTli_CertBinary = 206
  • SmAgentTli_CertUserDN = 207
  • SmAgentTli_ClientIp = 208
  • SmAgentTli_SessionSpec = 209
  • SmAgentTli_UserName = 210
  • SmAgentTli_UserPassword = 211
  • SmAgentTli_Reason = 212
  • SmAgentTli_AuthDirName = 213
  • SmAgentTli_AuthDirServer = 214
  • SmAgentTli_AuthDirNamespace = 215
  • SmAgentTli_UserMsg = 216
  • SmAgentTli_Server = 217
  • SmAgentTli_UserDN = 218
  • SmAgentTli_RealmCredentials = 219
  • SmAgentTli_FormLocation = 220
  • SmAgentTli_TransactionId = 221
  • SmAgentTli_CertIssuerDN = 222

// attributes 224 is reserved for custom agents

// Custom agents who wish to implement session timeouts must use these

  • attributes
  • SmAgentTli_IdleSessionTimeout = 225
  • SmAgentTli_MaxSessionTimeout = 226
  • SmAgentTli_DeniedRedirect = 227
  • SmAgentTli_DeniedText = 228
  • SmAgentTli_AcceptRedirect = 229
  • SmAgentTli_AcceptText = 230

One would probably ask, how is this useful to me while looking at the logs? The first thing to do is to is to make sure you've enabled the 'Message' field profiler on the Policy Server:

Setting the Message Field

Once you've done that, you should be able to see the following in the trace logs:

[10/12/2013][10:01:19][7028][][][][][][][][][][][][][iis7x_wa][Receive request attribute 200, data size is 8][mytest_poc_172_16_246_166_thn][] [10/12/2013][10:01:19][7028][][][][][][][][][][][][][iis7x_wa][Receive request attribute 217, data size is 34][http://localhost.coreblox.com][] [10/12/2013][10:01:19][7028][][][][][][][][][][][][][iis7x_wa][Receive request attribute 201, data size is 27][/smformsprotected/index.asp][] [10/12/2013][10:01:19][7028][][][][][][][][][][][][][iis7x_wa][Receive request attribute 202, data size is 3][GET][] [10/12/2013][10:01:19][7028][][][][][][][][][][][][][iis7x_wa][Receive request attribute 204, data size is 39][06-5cfde8b9-443e-4fe3-8162-cf9785cf66bc][] [10/12/2013][10:01:19][7028][][][][][][][][][][][][][iis7x_wa][Receive request attribute 205, data size is 0][][] [10/12/2013][10:01:19][7028][][][][][][][][][][][][][iis7x_wa][Receive request attribute 209, data size is 0][][] [10/12/2013][10:01:19][7028][][][][][][][][][][][][][iis7x_wa][Receive request attribute 212, data size is 4][][] [10/12/2013][10:01:19][7028][][][][][][][][][][][][][iis7x_wa][Receive request attribute 210, data size is 12][ADSiteminder][] [10/12/2013][10:01:19][7028][][][][][][][][][][][][][iis7x_wa][Receive request attribute 211, data size is 9][** Not Shown **][] [10/12/2013][10:01:19][7028][][][][][][][][][][][][][iis7x_wa][Receive request attribute 134, data size is 5][FALSE][]

All you need to do is to match up the 'Receive request attribute <value>' with the table above to get a sense as to what is being called.

The one thing you'll notice is that there is a 'gap' for the 17x values in the list above. Perhaps someone else has that list and if you do, please let me know and I'll add it to the list above.