RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
2019-01-10 02:33:23,209, [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'], (SystemfieldsUserAdministrationImpl.java:80), trace.com.rsa.ims.ocadmin.management.impl.SystemfieldsUserAdministrationImpl, ERROR, am82p.vcloud.local,,,,Failed to create systemfields user com.rsa.common.InvalidArgumentException: Failed to encrypt field com.rsa.pwd.auth.users
at com.rsa.ims.ocadmin.management.util.SystemfieldsWrapper.setTextField(SystemfieldsWrapper.java:106)
at com.rsa.ims.ocadmin.management.impl.AbstractSystemfieldsUsersAdministration.create(AbstractSystemfieldsUsersAdministration.java:68)
at com.rsa.ims.ocadmin.management.impl.SystemfieldsUserAdministrationImpl.create(SystemfieldsUserAdministrationImpl.java:73)
at com.rsa.ims.ocadmin.management.CreateOcAdminCommandExecutive.performExecute(CreateOcAdminCommandExecutive.java:51)
at com.rsa.ims.ocadmin.management.CreateOcAdminCommandExecutive.performExecute(CreateOcAdminCommandExecutive.java:
at com.rsa.command.TargetableCommand.performExecute(TargetableCommand.java:470)
at com.rsa.command.LocalTarget.executeCommand(LocalTarget.java:119)
at com.rsa.ims.command.LocalTransactionalCommandTarget.access$0(LocalTransactionalCommandTarget.java:1)
at com.rsa.ims.command.LocalTransactionalCommandTarget$2.doInTransaction(LocalTransactionalCommandTarget.java:268)
at com.rsa.ims.command.LocalTransactionalCommandTarget$2.doInTransaction(LocalTransactionalCommandTarget.java:1)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:131)
at com.rsa.ims.command.LocalTransactionalCommandTarget.executeCommand(LocalTransactionalCommandTarget.java:260)
at com.rsa.command.CommandServerEngine$CommandExecutor.run(CommandServerEngine.java:933)
at com.rsa.command.CommandServerEngine$CommandExecutor.run(CommandServerEngine.java:1)
at com.rsa.ims.security.spi.SimpleSecurityContextImpl.doAs(SimpleSecurityContextImpl.java:113)
at com.rsa.security.SecurityContext.doAs(SecurityContext.java:439)
at com.rsa.command.CommandServerEngine.executeCommand(CommandServerEngine.java:445)
at com.rsa.command.CommandServerEngine.executeCommand(CommandServerEngine.java:373)
at com.rsa.command.CommandServerBean.executeCommand(CommandServerBean.java:89)
at com.rsa.command.CommandServerEjb30_vraifm_CommandServerEjb30Impl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:34)
at com.rsa.command.CommandServerEjb30_vraifm_CommandServerEjb30Impl.executeCommand(Unknown Source)
at com.rsa.command.CommandServerEjb30_vraifm_CommandServerEjb30Impl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:701)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:231)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:527)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:523)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
Operations Console administrators provide predefined roles and have the permissions required to perform most of the tasks offered by the Operations Console.
As a workaround,
- From the Security Console navigate to Administration > Manage OC Administrators.
- Review those users who are listed as Operations Console administrators, checking for admins who no longer administer the deployment.
- Click Delete to remove the administrator then confirm by clicking OK.
- Once admins have been removed, new Operations Console admins can be added.
Refer to documentation on how to Add an Operations Console Administrator
To set logging to Verbose,
- Logon to the Security Console and navigate to Setup > System Settings.
- Under Basic Settings, select Logging.
- Select the server on which to enable logging and click Next. Note that if you choose the primary, there is an option on the next page to apply settings to all replicas.
- Set the Trace Log value to Verbose.
- Click Save.
Important: Do not set the trace logging level to verbose for extended periods of time unless instructed to do so by RSA Customer Support. Trace logs may occupy large amounts of disk space and this can impact system performance.
Related Articles
Supported web browsers report an error message when accessing RSA Authentication Manager 8.1 Security Console or Operation… 436Number of Views The aveksa.ear file fails to deploy on a WildFly cluster with an access denied error message in RSA Identity Governance & … 360Number of Views Authentication error with LDAP user assigned the Super Admin role while providing additional credentials to the RSA Authen… 213Number of Views RSA Authentication Agent API 8.5 for C Developer's Guide 72Number of Views AFX new or updated Connectors remain in a Deployed state and the MMC application fails to load in RSA Identity Governance … 194Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide