com.sun.identity.security.AMSecurityPropertiesException: AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.<br /> Check AMConfig.properties for the following properties<br /> com.sun.identity.agents.app.username<br /> com.iplanet.am.service.password<br /> Logging configuration class "com.sun.identity.log.s1is.LogConfigReader" failed<br /> com.sun.identity.security.AMSecurityPropertiesException: AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.<br /> Check AMConfig.properties for the following properties<br /> com.sun.identity.agents.app.username<br /> com.iplanet.am.service.password<br /> These errors didn't appear before the installation of Communication suite and the execution of the comm_dssetup.pl script. In the debug files of access manager we have : <u><strong>amAuthContext</strong></u> 04/21/2009 10:44:42:127 AM CEST: Thread[main,5,main] ERROR: Failed to obtain auth service url from server: http://agenda.cirad.fr:80 <u><strong>amLog</strong></u> 04/21/2009 10:44:42:988 AM CEST: Thread[main,5,main] ERROR: RemoteHandler.getLogHostURL(): 'null' is malformed. null amNaming 04/21/2009 10:44:42:128 AM CEST: Thread[main,5,main]<br /> ERROR: Naming service connection failed for http://agenda.cirad.fr:80/amserver/namingservice<br /> com.iplanet.services.comm.client.SendRequestException<br />

Oracle Community | 807573 | 8 years ago
  1. 0

    Access Manager 7.1 : FATAL ERROR: Cannot obtain Application SSO token

    Oracle Community | 8 years ago | 807573
    com.sun.identity.security.AMSecurityPropertiesException: AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.<br /> Check AMConfig.properties for the following properties<br /> com.sun.identity.agents.app.username<br /> com.iplanet.am.service.password<br /> Logging configuration class "com.sun.identity.log.s1is.LogConfigReader" failed<br /> com.sun.identity.security.AMSecurityPropertiesException: AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.<br /> Check AMConfig.properties for the following properties<br /> com.sun.identity.agents.app.username<br /> com.iplanet.am.service.password<br /> These errors didn't appear before the installation of Communication suite and the execution of the comm_dssetup.pl script. In the debug files of access manager we have : <u><strong>amAuthContext</strong></u> 04/21/2009 10:44:42:127 AM CEST: Thread[main,5,main] ERROR: Failed to obtain auth service url from server: http://agenda.cirad.fr:80 <u><strong>amLog</strong></u> 04/21/2009 10:44:42:988 AM CEST: Thread[main,5,main] ERROR: RemoteHandler.getLogHostURL(): 'null' is malformed. null amNaming 04/21/2009 10:44:42:128 AM CEST: Thread[main,5,main]<br /> ERROR: Naming service connection failed for http://agenda.cirad.fr:80/amserver/namingservice<br /> com.iplanet.services.comm.client.SendRequestException<br />
  2. 0

    Pls help: can't create suborganization using amadmin

    Oracle Community | 9 years ago | 807573
    java.lang.ExceptionInInitializerError
  3. 0

    SAMLv2 Plug-in on https

    Oracle Community | 8 years ago | 807573
    java.lang.ExceptionInInitializerError
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    SAMLv2 Plug-in on https

    Oracle Community | 8 years ago | 807573
    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
  6. 0

    adding another AM to existing setup

    Oracle Community | 8 years ago | 803038
    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

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.sun.identity.security.AMSecurityPropertiesException

      AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.<br /> Check AMConfig.properties for the following properties<br /> com.sun.identity.agents.app.username<br /> com.iplanet.am.service.password<br /> Logging configuration class "com.sun.identity.log.s1is.LogConfigReader" failed<br /> com.sun.identity.security.AMSecurityPropertiesException: AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.<br /> Check AMConfig.properties for the following properties<br /> com.sun.identity.agents.app.username<br /> com.iplanet.am.service.password<br /> These errors didn't appear before the installation of Communication suite and the execution of the comm_dssetup.pl script. In the debug files of access manager we have : <u><strong>amAuthContext</strong></u> 04/21/2009 10:44:42:127 AM CEST: Thread[main,5,main] ERROR: Failed to obtain auth service url from server: http://agenda.cirad.fr:80 <u><strong>amLog</strong></u> 04/21/2009 10:44:42:988 AM CEST: Thread[main,5,main] ERROR: RemoteHandler.getLogHostURL(): 'null' is malformed. null amNaming 04/21/2009 10:44:42:128 AM CEST: Thread[main,5,main]<br /> ERROR: Naming service connection failed for http://agenda.cirad.fr:80/amserver/namingservice<br /> com.iplanet.services.comm.client.SendRequestException<br />

      at com.iplanet.services.comm.client.PLLClient.send()
    2. com.iplanet.services
      WebtopNaming.getNamingProfile
      1. com.iplanet.services.comm.client.PLLClient.send(PLLClient.java:214)
      2. com.iplanet.services.comm.client.PLLClient.send(PLLClient.java:100)
      3. com.iplanet.services.naming.WebtopNaming.getNamingTable(WebtopNaming.java:640)
      4. com.iplanet.services.naming.WebtopNaming.updateNamingTable(WebtopNaming.java:678)
      5. com.iplanet.services.naming.WebtopNaming.getNamingProfile(WebtopNaming.java:603)
      5 frames