Authentication error while calling custom created Method via SOAP

Hi,

Have you seen this page? Web service calls

There is an example in it that can help checking your code.

Hope this helps,

Florent

HI Florent,

I tried , but getting below error while trying to call via javaScript

"the user/password authentication is not authorized for '******67' login via the '127.0.0.1' address"

Hi,

Your server is not accepting localhost ip address for authentication. check for allowed ip address in your server configurations. or try from authorized ip address.

Regards,

Amit

Thanks Amit,

So basically i need to register my IP in Server Configuration? but generally we don't set IP address. As i am able to use the same in Training environment   without any IP config.

Is there any parameter at Server Configuration to allow calls from intranet ?

Thanks

Nadeem

You need to whitelist the IP/range through security zones. or on that particular account on Operators.

Go to "Administration\Access Management\ Operators\%youracc%\ Access Rights\" then go to lower panel "Security settings" Edit the access parameters and start from there.

​more information here https://docs.campaign.adobe.com/doc/AC6.1/en/Technotes/AdobeCampaign_Deliverability_Configuring_Security_Zones.pdf

Security zones looks something like the following in serverConf.xml or config-yourinstance.xml

    <!-- Security zone 
       allowDebug :  Authorize debug mode for Web applications Default: false 
       allowEmptyPassword :  Authorize the user to use the application without a password Default: false 
       allowHTTP :  Authorize the use of HTTP for operator logon Default: false 
       allowSQLInjection :  Authorize the use of SQLDATA in expressions Default: false 
       allowUserPassword :  Authorize user/password session tokens Default: false 
       label :  Label Default: NewLabel() 
       name :  Internal name Default: NewName() 
       sessionTokenOnly :  Do not use the security token Default: false 
       showErrors :  Display error details Default: false -->
      <!-- subNetwork :  Sub-network 
         label :  Label Default: NewLabel() 
         mask :  Mask or address 
         name :  Internal name Default: NewName() 
         proxy :  Mask or address of (reverse) proxy used by this sub-network to access the instance. In this case, the 'X-Forwarded-For' header will be tested instead of this proxy. Default: 127.0.0.1 -->
      <!-- securityZone :   
         -->
  <securityZone allowDebug="false" allowHTTP="false" allowSQLInjection="false" label="Public Network"
                name="public">
    <subNetwork label="All addresses" mask="*" name="all" proxy="127.0.0.1, ::1"/>
    <securityZone allowDebug="true" allowHTTP="false" allowSQLInjection="false" label="Private Network (VPN)"
                  name="vpn" showErrors="true">
      <securityZone allowDebug="true" allowEmptyPassword="false" allowHTTP="true"
                    allowSQLInjection="false" allowUserPassword="false" label="Private Network (LAN)"
                    name="lan" sessionTokenOnly="true" showErrors="true">
        <subNetwork label="Lan 1" mask="192.168.0.0/16" name="lan1" proxy="127.0.0.1, ::1"/>
        <subNetwork label="Lan 2" mask="172.16.0.0/12" name="lan2" proxy="127.0.0.1, ::1"/>
        <subNetwork label="Lan 3" mask="10.0.0.0/8" name="lan3" proxy="127.0.0.1, ::1"/>
        <subNetwork label="Localhost" mask="127.0.0.0/8" name="localhost" proxy="127.0.0.1, ::1"/>
        <subNetwork label="Lan (IPv6)" mask="fc00::/7" name="lan6" proxy="127.0.0.1, ::1"/>
        <subNetwork label="Lan (IPv6)" mask="fe80::/10" name="lan6b" proxy="127.0.0.1, ::1"/>
        <subNetwork label="Localhost (IPv6)" mask="::1/128" name="localhost6" proxy="127.0.0.1, ::1"/>
      </securityZone>
    </securityZone>
  </securityZone>

Hi David ,

IP 127.0.0.1 is already masked at operator level ""Administration\Access Management\ Operators\%youracc%\ Access Rights\" then go to lower panel "Security settings" Edit the access parameters "

I will have to  look into serverConf.xml or config-yourinstance.xml .

Were you able to resolve the issue? I am having the same issue.

Hi Nadeem,

Could you find a way through?

Florent

Hi All,

I'm facing the same issue. We are on a hybrid model and marketing and frontal servers are not on the same system.

"the user/password authentication is not authorized for '******ar' login via the '0.0.0.0.0.0.0.1' address".

SessionToken is set to true in config file.

Thanks,
Vidya Shivakumar