Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
CMS-XML Unhandled exception when FIPS compliant algorithms is enabled
Unhandled exception when FIPS compliant algorithms is enabled
PDF Solutions Business Manager 11.8 Web Application Security Assessment White Paper
FIPS 140-2 compliance was enabled during all tests as well. This ensured that all encryption within SBM used FIPS 140-2 certified encryption libraries and FIPS 140-2 certified algorithms.
PDF ScalingfortheEnterprise
IdentityandAccessManagement SBMprovidessinglesign-on(SSO)authenticationoutoftheboxwhileinteractingwith componentsatruntimeanddesigntime.Italsoprovidesacompleteaudittrailofallinteractions andchangesthatareperformedbyeitherhumansorapplicationsduringasession. UserAuthentication RequeststotheSBMServerareauthenticatedusingoneofthefollowingschemes: – InternalPasswords UsercredentialscanbevalidatedagainstthosestoredwithinSBM.Passwordswithinthe SBMServerarestoredusingahashingalgorithm(SHA-256).Formoreinformation,see: fips / fips 180-2/ fips 180-2withchangenotice.pdf – WindowsDomainAuthentication TheWindowssecuritysystemintegratedintoIIScanbeusedtoauthenticateuseraccess. Inthiscase,IISverifiesloginnamesandpasswordsagainstWindowsuseraccounts.
PDF Scaling for the Enterprise
Passwords within the SBM Server are stored using a hashing algorithm (SHA-256). For more information, see fips / fips 180-2/ fips180-2withchangenotice.pdf.

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs