Page 1 of 1

Accessing WAM IPolicyClient

Posted: Tue May 17, 2011 2:44 pm
by tlmaravilla
Here is how we are currently access the WAM header info:

IPolicyClient ssoClient = WebApplicationPolicyClient.getPolicyClient();

long acctId = Long.parseLong(ssoClient.getPolicyAttribute(PolicyHeader.LDS_ACCT_ID));





When we first started with WAM, this was how they instructed us to get the data. Now that WAM has been integrated into the stack, is this still the prescribed way?

This way is working great, until someone internationally logs into our MTM client. Someone like:

Angel AnĂ­bal Cepeda Chicaiza

When we print the WAM data from our logs, the account name is UTF8 encoded:
2011-05-17 12:49:54,765 [FTX15090750] [INFO ] getUser() - LDS Account User Details: User Info: ldsAccountNm:angeluzelyte ldsPreferredNm:=?UTF-8?B?QW5nZWwgQW7DrWJhbCBDZXBlZGEgQ2hpY
2FpemE=?= ldsUnits:/7u176524/5u512028/ ldsAccountId:3512317026385640 ldsPreferredLang:es parentUnitNbr:512028 childUnitNbr:176524

It appear that this is a WAM issue, but it may be that our app needs to do something different. (see screen shot)
preferredNmIssue.jpg (15.68 KiB) Viewed 900 times

Posted: Tue May 17, 2011 4:59 pm
by YoungstromMJ
I think you're using "clientlib" currently. clientlib should be fine for continued use.

I know the Stack WAM integration does nothing to handle headers that are UTF-8 encoded like this. My WAM lead will be back in town on Thursday. I'll assign him to work with the WAM team and figure out what we should be doing in such a situation. I'll communicate with you and the client lib maintainer about what we find out. Thanks for identifying this. If this issue needs more urgent action then let me know:


Posted: Wed May 18, 2011 2:34 pm
by tlmaravilla
After working with Mark Boyd, turns out that we had an old clientLib. we are now using 1.28 and it looks good