Department is converting over to Windows-8 desktops this Fall, and we are starting to smoke-test the SAP Desktop applications under Windows-8.
Our Windows-8 OS defaults are set to be Federal Information Processing Standard (FIPS-140) compliant, which manage the acceptable cryptographic modules for hashing, etc.
When testing the BEx Query Designer 7.4 application, it application throws an error on the creation of a Calculated Key Figure (or formula).
We have discovered that this is because it uses the old (less-secure) MD5 hashing algorithm - which is not FIPS-140 compliant.
Has anybody in a Secure environment had this issue with the BEx Query Designer 7.4 application before..?
SAP Support don't seem to have any method for having the BEx Query Designer 7.4 application use a FIPS-140 compliant hashing algorithm (eg. SHA256, etc) - and seem to be treating the FIPS settings on the Windows-8 OS-Level as "non-standard"...which will probably be a "surprise" to their hundreds of thousands of users in the Public Sector.
Thanks in advance for any suggestions or advice on this "road-block".