Getting a Request could not be handled error when trying to change the certificate store on RSA Via Lifecycle & Governance 6.9.1 from the UI
Originally Published: 2016-05-16
Article Number
Applies To
RSA Product/Service Type: Access Certification Manager
RSA Version/Condition: 6.9.1, 6.8.1
Platform: Any
Issue
04/12/2016 10:59:21.597 ERROR (http-0.0.0.0-8445-7) [com.aveksa.UI] com.aveksa.gui.pages.base.data.dialog.EditableDialogPageData.handleRequest(EditableDialogPageData.java:46) -
com.rsa.crypto.InvalidAlgorithmParameterException: Could not DER encode the public key. (No OID for this transformation.)
at com.rsa.cryptoj.o.bk.a(Unknown Source)
at com.rsa.cryptoj.o.bk.a(Unknown Source)
at com.rsa.cryptoj.o.bk.a(Unknown Source)
at com.rsa.cryptoj.o.fr.getEncoded(Unknown Source)
at com.aveksa.server.certificates.CertificateManager.createCertificate(CertificateManager.java:128)
at com.aveksa.server.certificates.CertificateManager.createCertificate(CertificateManager.java:100)
at com.aveksa.server.certificates.CertificateManager.createCertificate(CertificateManager.java:86)
at com.aveksa.server.certificates.CertificateManager.createCertificateOfAuthority(CertificateManager.java:294)
at com.aveksa.server.certificates.CertificateManager.createCertificateOfAuthority(CertificateManager.java:279)
at com.aveksa.server.certificates.CertificateManager.createCertificates(CertificateManager.java:228)
at com.aveksa.server.certificates.CertificateServiceProvider.createServerCAAndKeyStore(CertificateServiceProvider.java:112)
at com.aveksa.server.certificates.CertificateServiceProvider.createServerCAAndKeyStore(CertificateServiceProvider.java:107)
at com.aveksa.gui.pages.admin.system.security.certificate.ChangeCertificateStorePageData.handleSubmit(ChangeCertificateStorePageData.java:53)
at com.aveksa.gui.pages.base.data.dialog.EditableDialogPageData.handleRequest(EditableDialogPageData.java:45)
at com.aveksa.gui.pages.PageManager.forwardRequest(PageManager.java:559)
at com.aveksa.gui.pages.PageManager.handleRequest(PageManager.java:323)
at com.aveksa.gui.pages.PageManager.handleRequest(PageManager.java:254)
at com.aveksa.gui.core.MainManager.handleRequest(MainManager.java:176)
at com.aveksa.gui.core.MainManager.doGet(MainManager.java:125)
at com.aveksa.gui.core.MainManager.doPost(MainManager.java:411)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.aveksa.gui.core.filters.LoginFilter.doFilter(LoginFilter.java:67)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.aveksa.gui.util.security.XSSFilter.doFilter(XSSFilter.java:20)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:701)Cause
Resolution
Related Articles
The request could not be handled error is thrown while editing a Change Request in RSA Identity Governance and Lifecycle 65Number of Views RSA DLP | Error "contact your administrator and reference error number with incremental number when trying to change the p… 23Number of Views 'Request could not be handled' error exporting metadata from RSA Identity Governance & Lifecycle 80Number of Views OPatch failure when individually applying Oracle patch 19509982 in RSA Identity Governance & Lifecycle 117Number of Views Error message "The request could not be handled" when attempting to edit a role in the New or Applied state in RSA Identit… 118Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?