4 Replies Latest reply: Oct 24, 2013 11:53 PM by iGenius RSS

    GG - Connecting to admin console

    user11180215
      Hi,

      When I try to log on to GG admin console i get an error:

      Failed to get login context. Perhaps your etc/gdsc-client.conf file is missing? : javax.security.auth.login.LoginException:java.lang.securityException:user admin, failed to be authenticated


      I installed web logic server prior to installing director software (2.0.0.3_007).
      I use a Java 1.6 u 20

      So, there is obviously a problem with login details, but this is the first time I am running the software, and the official tutorial says user:admin, pass:admin as a default login credential when running the console for the first time.

      Found nothing useful on metalink....am I missing something?

      Any thoughts?

      Thanks in advance
      Mario
        • 1. Re: GG - Connecting to admin console
          User152973
          See if this helps..


          Logon to Director v2.0 Admin Tool/Client returns error: ""Failed to get login context...." [ID 973711.1]

          --------------------------------------------------------------------------------

          Modified 07-SEP-2010 Type PROBLEM Status PUBLISHED

          In this Document
          Symptoms
          Cause
          Solution



          --------------------------------------------------------------------------------



          Applies to:
          Management Pack for Oracle GoldenGate - Version: 1.4.0.6 and later [Release: 1.4 and later ]
          Information in this document applies to any platform.

          Symptoms
          ISSUE:

          Logging on to the v2.0 Director GDSC Admin Tool or Director Client using User Name: admin Password: admin and Server: hostname is giving me an error:

          "Failed to get login context. Perhaps your etc/gdsc-client.conf file is missing? : javax.security.auth.login.LoginException:java.net.ConnectException: t3:/andross: No known valid part for : 'Default[t3]:t3(t3):null:-1:153.64.202.209:-1', No available router to destination "

          Cause
          *Director v2.0 requires the http port included in the Server string: <hostname>:<http port>*

          Solution
          *When logging on using the v2.0 Director Admin Tool or Director Client, the Server name entry must include the http port. So the string entered for Server should include:*


          *<hostname where director server is installed>:<http port>*


          *ie:*


          *andross:7001*

          *or if it is the current host:*

          *localhost:7001*
          • 2. Re: GG - Connecting to admin console
            user11180215
            Hello,

            Thanks for the try but, as I said...already saw this on metalink, but it's not my case. My case says "failed to authenticate", as if username or password is incorrect. This port bit I already tried. No success.


            Mario
            • 3. Re: GG - Connecting to admin console
              751488
              Make sure you start WebLogic from the directory created by Director Server install, **NOT** from the Oracle Middleware home.

              For example, from /u01/oracle/gg-director/domain/bin

              run ./startWebLogic.sh
              • 4. Re: GG - Connecting to admin console
                iGenius

                Hi,

                Please refer to the metalink documnet Doc ID 1461093.1

                Skip to content

                 

                 

                 

                 

                 

                 


                 

                 

                Jul 4, 2012PROBLEM

                 

                 

                 

                In this Document

                Symptoms
                Cause
                Solution
                References

                 

                APPLIES TO:

                Management Pack for Oracle GoldenGate - Version 11.1.1.1.0 and later
                Information in this document applies to any platform.

                SYMPTOMS

                On : 11.1.1.1.0 version, Director

                 

                When attempting to login to director client or web using username admin and password admin the following error occurs.

                 

                ERROR
                -----------------------
                Invalid username or password specified

                CAUSE

                When SQL Server is used as repository, a login to director client/web will fail or director server may crash with core dump. This is in jrockit

                 

                SOLUTION

                1. Log out of all director client and director web sessions

                 

                2. Stop the director server

                 

                  directorControl.sh stop

                 

                3. Login to weblogic console through
                  http://<server-name>:7001/console/

                 

                  The default username/password for this console is weblogic/weblogic

                 

                4. After successful login to weblogic console, do the following:-

                 

                  4.1 In the "Domain Structure" window, look for "Security realms" -- click

                 

                  4.2 Right side of the pan would show "ggRealm" -- click it

                 

                  4.3 Click on "providers" tab, it will show a table having
                  "gg-authenticator" -- click it

                 

                  4.4 Click on "provider specific" tab

                 

                  4.5 Look for "Group Membership searching" dropdown -- it is set to "unlimited"

                 

                  4.6 Change this to "limited"

                 

                  4.7 Click on "save" button

                5. Restart the director Server
                  directorControl.sh -b start

                 

                6. Try to login to director client or director web.

                REFERENCES

                @ BUG:13965768 - DIRECTOR SERVER INSTALLATION AGAINST SQL SERVER DUMPS CORE