Layer 7 Access Management

Upgrade Policy server to R12.52SP1CR1 caused WAMUI display incorrect 

04-14-2015 02:37 AM

Recently I have upgraded my policy server and WAMUI from R12.52 to R12.52SP1 and notice some strange behavior in WAMUI.

After upgrade both policy server and WAMUI, login to WAMUI and notice it was missing Federation tab.

R12.52 Windows Server 2008 R2 Enterprise x64 Edition-2015-04-14-15-00-15.png
In addition, under the Policies contains Realm and Password only:

R12.52 Windows Server 2008 R2 Enterprise x64 Edition-2015-04-14-16-24-41.png

 

 

In WAMUI server log, notice following error:

###

2015-04-14 14:59:57,808 INFO  [com.ca.CertificateDataStore] (http-drssoiam2.test.lab%2F127.0.0.1-8443-1) Logging initialized

2015-04-14 14:59:58,496 INFO  [com.ca.siteminder.uiagent.Connector] (http-drssoiam2.test.lab%2F127.0.0.1-8443-1) Establishing agent API connection for localhost

2015-04-14 14:59:58,746 ERROR [ims.rules] (http-drssoiam2.test.lab%2F127.0.0.1-8443-1) A number format exception was encounter transforming the values to longs for comparison. The values were [] and [1]. Returning false on evaluation.

2015-04-14 14:59:58,746 ERROR [ims.rules] (http-drssoiam2.test.lab%2F127.0.0.1-8443-1) A number format exception was encounter transforming the values to longs for comparison. The values were [] and [1]. Returning false on evaluation.

...

###

 

This issue can be resolved after re-run xpsddinstall SmMaster.xdd

 

R12.52 Windows Server 2008 R2 Enterprise x64 Edition-2015-04-14-15-09-03.png

 

 

Restart policy server and WAMUI after run xpsddinstall.

 

The WAMUI should display correctly as below:

 

R12.52 Windows Server 2008 R2 Enterprise x64 Edition-2015-04-14-16-35-29.png

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

11-23-2016 06:21 PM

As a general guideline, policy store issues (ie: corruption, data definition not being update after PS upgrade) could lead to WAMUI display issue.

Run xpssweeper and provide xpssweeper log for analysis should help to determine the status of policy store.

04-17-2015 02:36 AM

Reading this article, I have done a test:

 

I got the same error by upgrade from R12.x.

2015-04-17 16:07:46,128 ERROR [ims.rules] (http-PolicyServer%2F192.168.1.11-8443-1) A number format exception was encounter transforming the values to longs for comparison. The values were [] and [1]. Returning false on evaluation.

 

Then I run:

xpsddinstall SmMaster.xdd

XPSImport smpolicy.xml -npass


c:\Program Files (x86)\CA\siteminder\db>XPSImport smpolicy.xml -npass

[XPSImport - XPS Version 12.52.0100.499]

Log output: C:\Program Files (x86)\CA\siteminder/log/XPSImport.2015-04-17_163505.log

Initializing XPS, please wait...

Log Time Phase/Section                #Objects       %age        Elapsed

-------- ------------------------ --------------- -----------  -----------------

16:35:08 Initializing

16:35:08 Reading                                               00:00:00

16:35:08 Reading                                               00:00:00  00:00:00

16:35:08 Analyzing                      0/296                  00:00:00

16:35:08 Analyzing/Reference           11/296         3%       00:00:00  00:00:00

(ERROR) : [sm-xpsxps-02242] Object validation failed, class not present in data dictionary. XID: "CA.SM::SharedSecretPolicy@31-6dc899c1-2680-4660-ad34

-da7ca07438d2", Class: "CA.SM::SharedSecretPolicy" (Line:7694)

(FATAL) : [sm-xpsxps-01770] An error was encountered during import of policy data.

16:35:08 Complete                                              00:00:00

(FATAL) : [sm-xpsxps-05810] Import failed.

04-14-2015 08:23 PM

Hi Patrick, Hubert,

 

Yes, this is not a workaround. A lot of customer get confused that when upgrade the policy server, the policy store will get upgraded automatically.

This is the reason I create this doc to trace the symptom if policy store not being upgraded and Policy server, WAMUI get upgraded.

In fact, I should run xpsimport

ie:

XPSImport smpolicy.xml -npass

 

after xpsddinstall SmMaster.xdd to complete the policy store upgrade according to upgrade guide. However, I think in my use case (upgrade from R12.52 to R12.52SP1), the smpolicy.xml has not much different. If customer is upgrading from R12.x, they might need to run xpsimport after xpsddinstall as per upgrade guide.

 

Regards,

Kar Meng

04-14-2015 10:14 AM

Patrick rightly suggested above. I would just add a few words for clarity i.e. WAM UI should be upgraded last. Never upgrade the WAM UI without upgrading the PolicyStore. The Sequence of steps in documentation also suggest the same.

 

Regards

 

Hubert

04-14-2015 02:46 AM

Hi Kar,

 

This is not a workaround, passing from 12.52 to 12.52SP1, you need to upgrade the Policy Store.

 

Best Regards,

Patrick

Related Entries and Links

No Related Resource entered.