Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-480

Adding a server to a site requires restart of OpenAM

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Snapshot9, Snapshot9.5.2_RC1, 10.0.0, 11.0.0, 12.0.0
    • Fix Version/s: 13.0.0
    • Component/s: None
    • Labels:
    • Environment:
      Windows 2008 R2
      Oracle DS7
    • Support Ticket IDs:

      Description

      Try as I might, I cannot get ssoadm to work against OpenAM when I have a server contained within a site. When I remove the server from the site ssoadm starts to work again. I have followed the answer on the wiki about mapping the load balancer to the server name.

      -D"com.iplanet.am.naming.map.site.to.server=https://openssov.st3.local:443/opensso=https://st3sec2.st3.local:443/opensso"

      This has no impact. Also, I have tried without HTTPS and the same behavior exists. I can not see any traffic passing through the proxy at all (even though it can), so I am not sure what the intent of the above property is.

      I have tried having the same and different passwords for Directory Manager and amadmin and keeping them the same. All with the same effect.

      I have tried OpenAM9 and 9.5.2 both fail in the same fashion. I am trying to build a 100% silent install and this is a major problem. I have scripted the install of java, glassfish, Oracle DS, Opensso, ssoadmintools. But this is a show stopper for me and is becoming critical as time has all but escaped me.

      Executing class, com.sun.identity.cli.serverconfig.ListServers.
      Authenticating...
      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
      com.sun.identity.cli.CLIException: 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
      at com.sun.identity.cli.LogWriter.log(LogWriter.java:109)
      at com.sun.identity.cli.Authenticator.ldapLogin(Authenticator.java:169)
      at com.sun.identity.cli.AuthenticatedCommand.ldapLogin(AuthenticatedCommand.java:134)
      at com.sun.identity.cli.serverconfig.ListServers.handleRequest(ListServers.java:59)
      at com.sun.identity.cli.SubCommand.execute(SubCommand.java:291)
      at com.sun.identity.cli.CLIRequest.process(CLIRequest.java:212)
      at com.sun.identity.cli.CLIRequest.process(CLIRequest.java:134)
      at com.sun.identity.cli.CommandManager.serviceRequestQueue(CommandManager.java:598)
      at com.sun.identity.cli.CommandManager.<init>(CommandManager.java:196)
      at com.sun.identity.cli.CommandManager.main(CommandManager.java:160)
      CommandManager.<init>
      com.sun.identity.cli.CLIException: 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
      at com.sun.identity.cli.LogWriter.log(LogWriter.java:109)
      at com.sun.identity.cli.Authenticator.ldapLogin(Authenticator.java:169)
      at com.sun.identity.cli.AuthenticatedCommand.ldapLogin(AuthenticatedCommand.java:134)
      at com.sun.identity.cli.serverconfig.ListServers.handleRequest(ListServers.java:59)
      at com.sun.identity.cli.SubCommand.execute(SubCommand.java:291)
      at com.sun.identity.cli.CLIRequest.process(CLIRequest.java:212)
      at com.sun.identity.cli.CLIRequest.process(CLIRequest.java:134)
      at com.sun.identity.cli.CommandManager.serviceRequestQueue(CommandManager.java:598)
      at com.sun.identity.cli.CommandManager.<init>(CommandManager.java:196)
      at com.sun.identity.cli.CommandManager.main(CommandManager.java:160)

      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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rwapshott Robert Wapshott
                Reporter:
                chris.j.schultz chris.j.schultz
              • Votes:
                6 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: