UBP data not handled correctly
search cancel

UBP data not handled correctly


Article ID: 194595


Updated On:


CA Advanced Authentication - Strong Authentication (AuthMinder / WebFort) CA Strong Authentication CA Rapid App Security CA Risk Authentication CA Advanced Authentication


About  DE346932:
When user behavior model is configured, malformed exception is seen in UBP logs because of this error, model score is not calculated.
The defect flaw was fixed in 9.1.
However, the problem still  persists for attributes XUBPMobilityData1 and XUBPFrequencyData1


Release : 9.1

Component : RiskMinder(Arcot RiskFort)


Intentionally left "XUBPMobilityData0", "XUBPFrequencyData0" out of the fix. 

Because, "XUBPFrequencyData" does not grow in size by very much. It will never be beyond 4000 characters.

Whereas, "XUBPMobilityData" parameter stores data about the locations(longitude and latitude) from where transaction(login) is initiated. So, we keep appending "new" locations in this parameter. Practically, for any user, the number locations he/she may use for login are definite. It has a very less chance of growing beyond 4000 characters.  

Hence we have made modifications to handle only "XUBPDiscreteValueSet". Because this contains major information, such as hour of the dy, day of the week, day of the month, location information (city, state, country, continent) etc.,

So, this may not be a concern unless there are some end users who initiates login from very large number of new locations. But, we have not heard from any of our customers till now complaining about this. So, in reality this may not occur.