Admintokenaction Fatal Error Cannot Obtain Application Sso Token
Contents |
OpenDJ OpenIDM OpenICF OpenIG Intro to Identity Downloads Forums General Discussion ForgeRock Projects OpenAM OpenIDM OpenDJ OpenIG OpenUMA DevOps Internet of Things Documentation Groups Resources Events Calendar logging configuration class "com.sun.identity.log.s1is.logconfigreader" failed Upcoming Event Map Add Event! Issue with ssoadm tool after
Openam Admintokenaction Fatal Error Cannot Obtain Application Sso Token
setting up OpenAM site. Home Forums ForgeRock Projects OpenAM Issue with ssoadm tool after setting up check amconfig.properties for the following properties OpenAM site. Learn more about our upcoming Identity Summits This topic contains 4 replies, has 3 voices, and was last updated by gbairwa@scholastic.com 7 months, 1 ssoadm cannot obtain application sso token week ago. Author Posts March 26, 2015 at 10:42 pm #3745 PareshParticipant Hi, We are setting up OpenAM instance. The setup is done using "openam-configurator" tool. We have specified the same password for amadmin (ADMIN_PWD) and embedded OpenDJ "cn=Directory Manager" user (DS_DIRMGRPASSWD) in the configuration file. After the setup is complete, then we create a realm and configure bunch of other stuff using ssoadm tool. However, we have observed that after we setup a new OpenAM site and add the current OpenAM instance to this site, then we start getting an error for subsequent run of ssoadm tool. Here is the error message reported by ssoadm tool:
Mailing List Use Advanced Search to search the entire https://forgerock.org/topic/issue-with-ssoadm-tool-after-setting-up-openam-site/ archive. com.sun.identity.security.AMSecurityPropertiesException: AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token » Back to List Archive Chronological | Threaded « Previous Message Next » https://java.net/projects/opensso/lists/users/archive/2011-02/message/11 « Previous Thread Next » From:
Client SDK IssuesCommand-Line Utilities Issues 4079: ssoadm import-svc-cfg command fails when using Directory Server as the configuration data store 3955: Unable to execute the ssoadm command 2905: https://docs.oracle.com/cd/E19681-01/820-3745/ghtvv/index.html jss4.jar entry is missing in the ssoadm classpath 4079: ssoadm import-svc-cfg command fails when using Directory Server as the configuration data store Sometimes the import-svc-cfg subcommand fails because OpenSSO Enterprise cannot delete nodes in the Service Manager data store. The following scenarios can cause this problem: Configure OpenSSO Enterprise using a remote Sun Java System Directory Server cannot obtain as the configuration data store. Export the service XML file by using the ssoadm export-svc-cfg command. Re-import the service XML data obtained in Step 2 using the ssoadm import-svc-cfg command. When you are asked to delete the existing data, choose yes. The following error message is returned: Unexpected LDAP exception occurred. Workaround. Re-execute the ssoadm import-svc-cfg cannot obtain application command until it succeeds. 3955: Unable to execute the ssoadm command You are unable to execute the ssoadm command with the get-realm due to this exception. Logging configuration class "com.sun.identity.log.s1is.LogConfigReader" failed com.sun.identity.security.AMSecurityPropertiesException: AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token. Check AMConfig.properties for the following properties com.sun.identity.agents.app.username com.iplanet.am.service.password Logging configuration class "com.sun.identity.log.s1is.LogConfigReader" failed com.sun.identity.security.AMSecurityPropertiesException: AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token. Check AMConfig.properties for the following properties com.sun.identity.agents.app.username com.iplanet.am.service.password AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token. Check AMConfig.properties for the following properties com.sun.identity.agents.app.username com.iplanet.am.service.password Check if the amadmin password is different from the directory manager password for the service management data store. If yes, apply the following workaround. Workaround. Modify the server configuration XML as follows: Log in to the OpenSSO Console as amadmin. Use the ssoadm.jsp get-svrcfg-xml to get the server configuration XML. Use encode.jsp to encode the amadmin password. Set the encoded password in the two places represented by amadmin-password in the XML. For example: