000034577 - Passmark STU(Site To User) Startup Issue in RSA Adaptive Authentication(on Premise) 7.2

Document created by RSA Customer Support Employee on Dec 20, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000034577
Applies ToRSA Product Set: Adaptive Authentication (OnPrem)
RSA Version/Condition: 7.2
 
IssueCustomer was getting the following error in aa_server.log 
 
ERROR [http-8443-2] [] [] [com.rsa.stu.core.ws.handler.SiteToUserWSHandlerImpl] - <com.rsa.stu.core.exceptions.STUWSException: 
Reason Code: 1101 
Description: Configuration Error
CAUSE: Configuration framework is not loaded; check the alarm logs.>
com.rsa.stu.core.exceptions.STUWSException: Reason Code: 1101
Description: Configuration Error
CAUSE: Configuration framework is not loaded; check the alarm logs.
at com.rsa.stu.core.validator.STUValidatorList.validateList(STUValidatorList.java:105)
at com.rsa.stu.core.ws.handler.GenericHandler.validateRequest(GenericHandler.java:102)
at com.rsa.stu.core.ws.handler.SiteToUserWSHandlerImpl.query(SiteToUserWSHandlerImpl.java:21)
at com.rsa.stu.ws.processor.STUDelegate.query(STUDelegate.java:15)
at com.rsa.stu.ws.axis.generated.SiteToUserSkeleton.query(SiteToUserSkeleton.java:29)
at com.rsa.stu.ws.axis.generated.SiteToUserMessageReceiverInOut.invokeBusinessLogic(SiteToUserMessageReceiverInOut.java:49)
at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)

 
ResolutionInstallation Prerequisites for Tomcat was missed, making the following changes resolved the issue
 
1. Locate the java.security file in the path_to_JRE/lib/security directory
and open the file for editing.
2. Locate the following line:
securerandom.source=file:/dev/urandom
and change it, as follows:
securerandom.source=file:/dev/random
3. Locate the section that looks similar to the following:
security.provider.1=sun.security.pkcs11.SunPKCS11
${java.home}/lib/security/sunpkcs11-solaris.cfg
security.provider.2=sun.security.provider.Sun
security.provider.3=sun.security.rsa.SunRsaSign
security.provider.4=com.sun.net.ssl.internal.ssl.Provider
security.provider.5=com.sun.crypto.provider.SunJCE
security.provider.6=sun.security.jgss.SunProvider
security.provider.7=com.sun.security.sasl.Provider
security.provider.8=org.jcp.xml.dsig.internal.dom.XMLDSig
RI
security.provider.9=sun.security.smartcardio.SunPCSC
4. Move the SunPKCS11 security provider to the end of the list and renumber, as
follows:
security.provider.1=com.ibm.crypto.provider.IBMJCE
security.provider.2=com.ibm.jsse2.IBMJSSEProvider2
security.provider.3=com.ibm.security.jgss.IBMJGSSProvider
security.provider.4=com.ibm.security.cert.IBMCertPath
security.provider.5=com.ibm.security.cmskeystore.CMSProvi
der
security.provider.6=com.ibm.security.jgss.mech.spnego.IBM
SPNEGO
security.provider.7=com.ibm.security.sasl.IBMSASL
security.provider.8=com.ibm.xml.crypto.IBMXMLCryptoProvid
er
security.provider.9=com.ibm.xml.enc.IBMXMLEncProvider
security.provider.10=org.apache.harmony.security.provider
.PolicyProvider
security.provider.11=com.ibm.crypto.pkcs11impl.provider.I
BMPKCS11Impl

 

Attachments

    Outcomes