Automic Workload Automation

Expand all | Collapse all

Unable to login to application through encryped password

  • 1.  Unable to login to application through encryped password

    Posted 05-15-2018 10:10 AM

    Hello All,

     

    We have encrypted password using LOGIN object to login to Hyperion application.

     

    we have used below command to call password in job. (Eg: --iyo7yhjhl8767hu)

     

    :SET &pwd# = GET_LOGIN(LOGIN.PWD,"*",STORE,PASSWORD)

     

    The job calls the password, but is failing due to invalid password error.

     

    Could any one let me know what is missing here.

     

    Thanks in advance



  • 2.  Re: Unable to login to application through encryped password

    Posted 05-15-2018 03:15 PM

    Hi

     

    The decryption of the job messenger is missing here.

     

    The password is returned in encrypted form. You can use the password with the Job Messenger (start parameter CMD) where it will be decrypted.

     

    Docu:

    Automic 

     

    cheers, Wolfgang



  • 3.  Re: Unable to login to application through encryped password

    Posted 05-15-2018 04:10 PM

    Hi Brueckler,

     

    Thank you for the reply.

     

    I tried below as well which gives the same error.

     

    :SET &pwd# = GET_LOGIN(LOGIN.PWD,"*",STORE,PASSWORD)

    &UC_JOBMD CMD = "script.sh &pwd#"

     

    When I see the report, I see first line as

    c:\>CMD = "script.sh --iyo7yhjhl8767hu"

     

    and the 'pwd' value is the same encrypted password. Am i missing anything here.

     

    Thanks in advance



  • 4.  Re: Unable to login to application through encryped password

    Posted 05-15-2018 04:39 PM

    I think you have to remove the spaces from around the equal sign like so;

     

    &UC_JOBMD CMD="script.sh &pwd#"

     

    If this works, you should still see --iyo7yhjhl8767hu on the displayed command, but UC4 will decrypt it when it executes the command.

     



  • 5.  Re: Unable to login to application through encryped password

    Posted 05-15-2018 04:46 PM

    Hi Peter,

     

    Tried without space as well. As you said, I see encrypted password in the report, but fails with same invalid login error.

    Thanks



  • 6.  Re: Unable to login to application through encryped password

    Posted 05-15-2018 04:59 PM

    I just realized your results are consistent with the variable &UC_JOBMD being empty.  I have seen this myself when I use it from objects that don't populate it naturally.  For instance this happens to my windows jobs if I'm using the interpreter option.  Suggest you print its contents to be sure.

     

    When this happens here, the solution has been to populate it myself like so (for windows jobs);

     

    :   set &UC_JOBMD = "C:\path_to_where_it_lives\UCXJWX6M.EXE"



  • 7.  Re: Unable to login to application through encryped password

    Posted 05-15-2018 11:56 PM

    Thank you Peter. This took me to next step and I'm able to print decrypted password even.

     

    But, I now see below error when I use '&UC_JOBMD CMD="script.sh &pwd#"'

     

    'script.sh' is not recognized as an internal or external command,



  • 8.  Re: Unable to login to application through encryped password

    Posted 05-16-2018 12:06 AM

    Able to get to script.sh, but see this error

     

    Program 'UC4 Job Messenger' version '11.2.7+build.955' started
    Error 'Unable to connect agent', reason: 10049 - The requested address is not valid in its context.



  • 9.  Re: Unable to login to application through encryped password

    Posted 05-18-2018 05:50 AM

    I can not offer a solution, just a pointer:

     

    10049 is an error code from the BSD tcp/ip stack (which is also used on Win32). Automic even documents these, because they simply pass them on:

     

    https://docs.automic.com/documentation/webhelp/german/ALL/components/AE/11.2/All%20Guides/Content/ucaalq.htm

     

    (sorry, I can't find this the English version of this page, but the German version is half English anyway, so ... )

     

    A network name is wrong, e.g. a host name does not exist, there was a DNS failure, an IP address is wrong etc.

     

    You may want to look for the source of the problem with this in mind. Possibly check the configuration of your Automic agent and DNS resolution for any obvious problems.

     

    You didn't tell us what platform you are on (as far as I see), but if you're on a UNIX-like platform, strace or truss or any similar utility may also provide hints to the problem, but this is an advanced technique. If you strace the agent, look for the 10049 error from the kernel, then trace it backwards to identify the failing network ressource.

     

    Hth,