SSRS Windows Authentication Login

Hi guys, I have been battling with this issue for the past 2 days. 
I have deployed my ssrs reports to my test server. 
Anytime I try to  access the report manager or reportserver url from another client pc, I am being prompted with a Windows Security Login. 
My client user isn't an part of the domain, but I want to disable that Windows Security prompt
Steps I have taken
1. I changed the rsreportserver config authentication type to <RSWindowsNTLM> 
2. I have added an execution account(Local administrator) in the Report Configuration Manager
3. I have added the Credentials Stored Securely on the report server settings.
After doing all this, I am still prompted with the Windows Security.
Please What Do u thing I am missing here?
Guys I am counting on you.

Hi earlgood77,
As the error message said, the issue occurs because the remote SMTP server requires authentication, however, the report server is configured to use Anonymous authentication. To address this issue, we can create a virtual SMTP server on the report
server computer which has IIS and IIS Manager installed, and relay mail to the desired SMTP server. 
Mike Yin
TechNet Community Support

Similar Messages

  • My MacBook Pro Retina's Bluetooth chipset unknown/odd login message on the login screen states Login Window Authentication Login window Name edit text has keyboard focus. In addition, the login screen is not remembering me

    I have been experiencing several issues with my MacBook Pro Retina mid 2012. My MBPR is scheduled to go into the depot. However, I am wondering if anyone may be able to shed light on a few issues as this is the third "official" time my MBPR is going back for service ("one depot" trip; "one authorized" dealer; several in-store visits).
    My Bluetooth is stating that the Bluetooth Chipset is Unknown (0). I also have had Bluetooth Preferences mysteriously change on me. In addition, while Bluetooth is off there are two serial modems turning on. I have turned them off, but they continue to pop up.
    In addition, when I log in, my MBPR is not remembering me and my login name is not appearing on the slate-gray screen. The name and password are blank and the following message appears in the lower left hand corner. "login window authentication login window Name edit text has keyboard focus."  As a side note, I am the only user. The login issue is a recent occurrence as we just totally wiped it again via a Command + R, and I don't believe I have an accessibility setting set to anything that would cause this, but wanted to check.
    Should I be concerned here? Has anyone else had issues like this? I don't want to worry if I don't have to. I have had so many issues over the course of nine months. 5-6 wipes. Airport card replaced and I am about to pull my hair out if my MBPR doesn't come back worldly like clock work this time. I just can't send my days trying to get a $2300 product to work for me any longer. No idea what is wrong with it, but it is driving me insane. Cross your fingers for me and any guidance you have or thoughts would be welcomed. Thank you. EMM

    A few more issues...
    In Console, the following is greyed out:
    User and Diagnostic reports
    *[user logs are accessible]
    My guest files are locked, but again I am the administrator of MBPR.
    I am worried about a keystroke logged or at least, trying to rule it out.
    Mdworker32(225) [and other mdworker numbers] are sandboxing; stating deny Mach-lookup, etc. long attachment with those files with version: ??? (???).
    Postinstall: removing applications/Microsoft Office 2011/Microsoft
    WARNINGS in Console include:
    [NSImage compositeToPoint:fromRect:operation:fraction:] is deprecated in MacOSX 19.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction] instead.
    There are a ton of other warnings. Before I go through this again, can someone tell me if this is normal (all of it -- above too); or if these are symptoms is a keystroke logger or hardware issues? 
    I ask because originally, when my computer went in for diagnostics (more than once), Apple stated the hardware was fine (other than Airport Card -- finally). However, if I've done 5-6 total wipes; created new users; do not have sharing set-up; have not played around in Terminal; and am up-to-date with versions -- and various issues KEEP COMING BACK -- I am left wondering if a keystroke logger would be possible here?!? I thought maybe a faulty logic board, but why would diagnostics be okay, then? Not trying to be hyperbole, just desperate.
    Please help me rule keystroke logger out or at least, tell me so I know, so I can take appropriate action. If you think it could be the logic board with symptoms above, that would be a great too.
    All I want to do is use the computer as intended, but I can't seem to get a real answer, so after nine months -- I am turning to the communities to see if anyone -- anyone at all -- can help. The last thing I can do is have the MBPR come back from the depot and the same thing occur. Any guidance or advice would be so gratefully appreciated.

  • Windows Authentication login cannot access backup files stored in Users\[User] folder.

    I am currently logged in to my database engine using SSMS and Windows Authentication; specifically, I am logged in with Joe-PC\Joe, where Joe-PC is the domain name of the machine hosting the database, and Joe is the user that created the database. 
    If it matters, I am running all of this locally from Joe-PC.
    I have a .bak backup file stored in my C:\Users\Joe\Desktop folder that I am trying to restore.  However, I get an error saying 'Either the location does not exist, or the current login account does not have access to it.'  I am certain the location
    exists, as I am looking at it right now, and I can't see why Joe-PC\Joe wouldn't have access to it's own user folder. 
    I am absolutely baffled as to why this is behaving this way.  I am fully aware that I can work around the issue, but I'd like to know why this isn't working as it seems like it should.  Does the Windows Authentication that SQL Server uses not have
    the permissions that the account would normally have?  Is the Windows Authentication user even the same thing as the user that logs into Windows?  What else could be going on that I don't understand?

    Thanks for your answer.  My user account is one of two administrator accounts on this computer (the other is only set up for consistency sake, and has probably only been logged into a total of 5 times; all of our computers have the account though, so
    I thought I should put it on here as well).  The issue isn't that my account doesn't have restore permissions, just that SSMS can't access the user folder when logged in using Windows Authentication.  Another issue that I assume is related results
    in a lack of permissions on backup files until I manually set permissions to 'Everyone' under the backup file's properties\security tab.  Also, not sure if it matters, the backup is taken from a customer's computer running Win 7 Pro x86 while my computer
    is on Win 7 Ultimate x64.
    Not sure if this helps pinpoint the issue, but my current workaround is as follows:
    Copy the .bak file to the C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.WSA\MSSQL\Backup (default backup folder)
    Right-click the .bak file and go to the properties toolbox.  Select the Security Tab, give full permission to 'Everyone'.
    In SSMS, select 'Restore Database' after right-clicking on 'Databases' in left-hand tree.
    Give the DB a name, restore from device, select my file.
    This method hasn't failed me yet, but any deviation (other than setting permissions before or after moving) causes me to get access errors when I try to restore.  Fortunately, this isn't a production database engine, just a testing environment, but
    I'd like to get an idea of what's going on, because I know it's only a matter of time before I or a customer runs into this issue.

  • SQL and windows authentication login

    Please clear my doubt.
    If login is windows authntication, we can not lock and expire that account right. We can just disable that account.
    We can not do lock the account manually, if it is windows and sql logins.
    Please clear my doubt

    Hello Shashikala,
    In SQL Server you can manually disable a Windows and SQL Logins, but you can't lock them, you only manually unlock a SQL Login.; a SQL Server Login can be locked by SQL Server, if e.g. the password period has expired.
    Windows Logins can also be locked, but that happens on OS / AD level, not on/from SQL Server.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • Windows Authenticated User Login

    Hi All,
    Does anybody know if there are plans to incorporate Windows Authenticated Login to SAP Business One in the future?
    We have many customers who ask this question - why should people have to remember a windows login AND one to B1?
    If this is not yet planned for release, could you please consider it?
    Many thanks

    Hi Vikas
    As Patrick mentioned, there is no native support built into the ABAP AS for LDAP authentication via SAPGUI.
    As an option and If you have SAP Identity Management you could look at deploying the password hook, this provides an enterprise password of same password approach. Hence end users can enter their MSAD password to gain access to SAP via SAPGUI - it works well.
    SAP Identity Management : Password Hook Configuration Guide
    The SAP NetWeaver Identity Management Password Hook is a password hook DLL that can be installed on the Microsoft domain controller(s) in the password verification chain. The hook intercepts password changes in the Microsoft domain and distributes it to other applications using the SAP NetWeaver Identity Management Identity Center.
    Hope it helps.


    I had an error while executing appcation from IIS as follows
    Login failed for user 'IIS APPPOOL\ASP.NET v4.0'.
    An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
    Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'IIS APPPOOL\ASP.NET v4.0'.
    [SqlException (0x80131904): Login failed for user 'IIS APPPOOL\ASP.NET v4.0'.]
    Can the above problem be solved by CREATING WINDOWS AUTHENTICATION LOGIN FOR
    'IIS APPPOOL\ASP.NET v4.0'  ?
    If yes, how to create the login?
    If no,what is the best possible solution?
    Please reply as soon as possible as i am unable to run my project which I had done in my lab,in my home system.

    Hi Praveen,
    To fix this issue, you need to change the Identity of your website's Application Pool to use the
    NetworkService account (or the less secure LocalSystem account).  By default, IIS7 seems to set the Application Pools Identity to 'ApplicationPoolIdentity' instead of NetworkService or LocalSystem.
    Here's a step-by-step guide for determining your websites Application Pool, then changing its Process Model Idenitty in IIS7:
    1.Open Internet Information Services (IIS) Manger.
    2.In the Connections sidebar, drill down into Default Web Site and click on your website.
    3.Now in the Actions sidebar (on right side), click on Advance Settings... In the popup box, under General you will see your Application Pool listed for your website (in my case the app pool is: ASP.NET V4.0).
    4.Click Cancel...  If you choose, you can change the Application Pool here, but for the sake of this example we just wanted to find out what the website's App Pool was.
    Then change the app pool's (Process Model) Identity to 'NetworkService', the steps are showed as below:
    1.Open Internet Information Services (IIS) Manger.
    2.In the Connections sidebar, click on Application Pools.
    3.Now right-click on theApplication Pool that your website is using (in this case my site is using the ASP.NET v4.0 application pool), and select Advanced Settings... from the menu.
    4.In the Advanced Settings pop-up box, locate the Process Model -> Identity section and click on the Application Pool Identity.
    5.In the Application Pool Identity pop-up box, change the Built-in account to NetworkService (or if you want LocalSystem), then click OK, and click OK again to save your Advanced Settings changes.
    Hope this helps.
    Best Regards,
    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Is there any way to add SQL Server 2008 R2 "SQL Authentication" logins to SQL Server Integration Services

    Hi Experts, 
    We have a way to add the Windows Authentication-logins /OS users  in SSIS
    Component Services -> Computers -> My Computer -> DCOM Config -> MSDTSServer
    Right click on MSDTSServer
    Click properties
    Click on the Security tab
    Select Customize and add the users/groups to the Launch/Activation and Access tabs accordingly
    Add the user to the local Distributed COM Users group
    Restart the SSIS service
    +++But do we have a way to add SQL Server Authetication logins to SSIS, Please clarify me 
    Prem Gokull

    Hi PREM,
    If I understand correctly, you want to use SQL Server Authentication log to SQL Server Integration Services.
    Based on my research, only Microsoft Windows Authentication is available for SSIS. So we cannot use SQL Server Authentication log to SQL Server Integration Services. Besides, we can only add OS users in the DCOM Config permission area.
    Connect to Server (Integration Services)
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication" on SQL Server 2008 R2 Enterprise Edition 64-bit SP2 clustered instance

    Hi there,
    I have a Windows 2008 R2 Enterprise x64 SP2 cluster which has 2 SQL Server 2008 R2 Enterprise Edition x64 SP2
    A domain account "Domain\Login" is administrator on both physcial nodes and "sysadmin" on both SQL Server instances.
    Currently both instances are running on same node.
    While logging on to SQL Server instance 2 thru "Domain\Login" using "IP2,port2", I get error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication". This happened in the past
    as well but issue resolved post insatllation of SQL Server 2008R2 SP2. This has re-occurred now. But it connects using 'SQLVirtual2\Instance2' without issue.
    Same login with same rights is able to access Instance 1 on both 'SQLVirtual1\Instance1' and "IP1,port1" without any issue.
    Please help resolve the issue.

    I Confirm that I encountred the same problem when the first domain controller was dow !!
    During a restarting of the first domain controller, i tried to failover my SQL Server instance to a second node, after that I will be able to authenticate SQL Server Login but Windows Login returns Error 18452 !
    When the firts DC restart finishied restarting every thing was Ok !
    The Question here : Why the cluster instance does'nt used the second DC ???
    Best Regards     

  • SP2013 SSRS 2012 repor service add-in always uses NT authority\anonymous instead of windows authentication

    We are building a SP2013 farm with SQL2012 and the SSRS 2012 add in , looking at the rsreportserver.config we have added the parameter RSWindowsNegotiate as listed below. 
    < /AuthenticationTypes>
    We have followed this article ( where the following is listed:
    ASP.NET must be configured for Windows Authentication. By default, the Web.config files for the Report Server Web service and Report Manager include the <authentication mode="Windows"> .
    However looking at the web.config of the report server the following parameters * (see below)are present but
    not the authentication mode='windows', only <windowsAuthentication enabled="true" /> is listed. 
    * <security>
            <anonymousAuthentication enabled="false" />
            <windowsAuthentication enabled="true" />
    The report server is operational as long as we use datasources  located on the same farm but as soon as try to utilize a datasource outside the farm the report server uses anonymous to access the datasource. We have configure the c2wt services and have
    the proper spn's in place on the domain , so we should not be suffering from the double hop issue.
    How do we configure the reportserver to accept windows authentication?
    Any help is welcome.

    Thanks for your reply, The web application is configured to use Kerberos and the spn has been created for the web application account.Yes I do receive a Kerberos ticket when I access the web application:
    Client: myuser @ DOMAIN.COM
    Server: HTTP/webapp @ DOMAIN.COM
    KerbTicket Encryption Type: RSADSI RC4-HMAC(NT)
    Ticket Flags 0x40a40000 -> forwardable renewable pre_authent ok_as_delegate
    Start Time: 1/3/2014 13:08:26 (local)
    End Time:   1/3/2014 23:03:42 (local)
    Renew Time: 1/13/2014 13:03:42 (local)
    Session Key Type: RSADSI RC4-HMAC(N
    What we do not understand is why the reporting service application will only work when it uses :
    identity impersonate="false" & anonymousAuthentication enabled="true"
    when we change the identity impersonation to true we cannot access the reporting services system settings in the CA anymore and receive an error message:
    "The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database"

  • SQL Windows Authentication with Login of AD Group 'Domain Admins'

    Having a bit of a difficulty with Microsoft SQL Server 2012 windows authentication integration...
    The server is setup to have Windows authentication used as its means of login authentication. No issues with this other than a strange error that occurs on multiple SQL servers in our domain: 
    When a login is created for domain group "[domain]\Domain Admins", users within this AD group cannot connect to the SQL server through the Management Studio. The error that SQL server gives is Error 18456, Sate 11, i.e. "Valid login but server
    access failure"
    However when a different AD group is added as a login (like [domain]\[group]), users from this group can successfully log into SQL server. It seems that adding any other group, even groups from a different domain, grants successful authentication as I would
    expect EXCEPT the AD group 'Domain Admins".
    Is there some restriction/security feature at play here on this AD group that makes using the 'Domain Admins' group as a login not possible? 

    Yes, this group was removed and readded just yesterday to try to fix the issue.
    Here is the output of the command:

  • Retain Windows authentication but allow re-login as another user

    I have been reading all about Login as a different user being disabled, the use of loginasanotheruser and how this is not recommended for later browser.  Here is my situation that I am at a loss to resolve. 
    All of our users connect to SharePoint using Windows authentication. This needs to remain.  However in our board room we have a number of computers all logged in with a common windows user account.  Executive meetings are confidential and
    we do not want to allow access to their site by the common Windows user - they must user their own login.  Normal browsing is to retain the Windows authentication however when they come to the executive SharePoint site we need to present a login before
    they progress. 
    I have seen comments on using "runas.exe" or the "Run as" option on shift-right click.  The trouble is that we do not know which participant will sit at a particular seat/computer in the room.  Our executive want everying by
    minimal clicks and complexity.  The expectation is that they enter the room and the site login page is already displayed as they arrive.
    So any ideas?  This one has me stumped.

    You could have a little batch file that asks for username and password then runs the 'runas.exe' with those details. That does the same thing as leaving a login page lying around.

  • Users using Windows Authentication unable to login after upgrade to SQL Server 2012 SP2 CU1

    We upgraded from SQL Server 2008 R2 to SQL Server 2012 SP2 CU1.  Upgrade was successful.  Users that have SQL Server Management Studio 2012 can successfully log in via Windows Authentication, but users with an older version of SQL Server Management
    Studio are unable to log in via Windows Authentication. 
    The error they receive is listed below:
    Connect not connect to XXXXXXX
    Login Failed.  The login is from an untrusted domain and cannot be used with Windows Authentication. 
    (Microsoft SQL Server, Error: 18452)
    If we switch to Mixed authentication, users can log in via SQL Server Authentication.
    Our security policy prohibits SQL Authentication. 
    Outside of having the staff upgrade to SQL Server 2012 SQL Server Management Studio, is there any setting I can set/unset to allow older version of SQL Server Management studio to connect to SQL Server 2012?

    Glad to see that you were able to resolve the issue yourself, but for the curious, could you explain what this
    Extended Protection is?
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

    I have gone through couple of posts regarding this issue but couldn't get the right solution. Could you please help what exactly we are missing here.
    1) we have two SQL instances on one standalone machine (Default Instance (2008 SP3) + Named Instance (SQL 2012 SP1))
    2) Both instances are configured to accept SQL+ Windows authentication.
    3) when we give access to our users they are getting following exception if they connect with 'windows authentication'. (For both instances)
    Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
    Note: (Being a sys + windows admin I'm able to connect both the instances from same client machine without
    any issues)
    4) Also, we observed following error in windows application event log,
     SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure.
    The logon attempt failed   [CLIENT:]
    5) If we create SQL login it is working fine without any issues.
    Could someone guide/help  me identifying and fixing this issue.
    Thank you

    Are those Windows Logins associated to domain Windows accounts? Windows Logins work for domain accounts and local Windows account created on the server where the SQL Server instance is installed (and used to login locally to the server).
    Could you try to delete one of the Windows logins that fail to login , and try to recreate them?
    The following resources may help:
    Hope this helps.
    Alberto Morillo

  • To get a SYSTEM NAME even using sa or Group login other than Windows Authentication

    how to get system name in username when we write a select query Select SUser_sname() in sql server 2008 r2.
    Actually , requirement  is  I have to give a sql serevr login to the client.
    NOTE : I cant create a Windows Authentication to the client.
    So, I create a login Called    Satish with Password
    [email protected]  ,
    when client login with Satish , and if he selects a  Select SUser_sname()  he will get a
    Satish as Output , but my requirement is i have to display a
    client name(System Name).
    Very Urgent , Please do me need full.

    You may refer here:
    CREATE LOGIN login1 WITH PASSWORD = 'J345#$)thb';
    CREATE LOGIN login2 WITH PASSWORD = 'Uor80$23b';
    CREATE USER user1 FOR LOGIN login1;
    CREATE USER user2 FOR LOGIN login2;
    --Give IMPERSONATE permissions on user2 to user1
    --so that user1 can successfully set the execution context to user2.
    --Display current execution context.
    -- Set the execution context to login1.
    EXECUTE AS LOGIN = 'login1';
    --Verify the execution context is now login1.
    --Login1 sets the execution context to login2.
    EXECUTE AS USER = 'user2';
    --Display current execution context.
    -- The execution context stack now has three principals: the originating caller, login1 and login2.
    --The following REVERT statements will reset the execution context to the previous context.
    --Display current execution context.
    --Display current execution context.
    --Remove temporary principals.
    DROP LOGIN login1;
    DROP LOGIN login2;
    DROP USER user1;
    DROP USER user2;

  • How to configure Axis stubs for Integrated Windows Authentication ?

    Hi All,
    I am trying to consume a web service on https and it uses .NET with Integrated Windows Authentication Security Mechanism. When I type the web service endpoint address in browser I am prompted for a login dialog and I login using username (in the format <domain name>\\<username>) and password given by the web service provider.
    Now I have generated stubs using AXIS 1.2 Final but I dont know how to pass or set the credentials (domain, username, password) in my client program. I tried <stub object>.setUsername and <stub object>.setPassword methods but I am not able to connect to the service and I always get HTTP Error Code 401.2 from the service. I am not sure this is right way to set credentials in my code. I tried searching this mailing list but no avail. Can anyone please help me.
    Thanks & Regards,

    Hello all - I ran into this and spent way too much time looking for the answer, however this is how I got it to work. My code was specific to getting SSRS authenication working so it should work with any NTLM authenciation via HTTP. setAuthenticateProperty() actually does the enabling of NTLM.
    * Sets up the needed information to enable NTLM authentication for SOAP/HTTP calls..
    * @author Brian Hayes
    public class NTLMAuthenticator {
        private Authenticator authenticator;
        private String username;
        private String password;
        private String domain;
        private String host;
        private URL wsdlurl;
         * Uses the endpoint.getHost() as the host name to use for authentication.
         * <li> Generally the endpoint host is the target for actual authenciation.
         * <br>
         * @param endpoint -
         *            The URL location of SSRS ReportExecution2005 wsdl.
         * @param username -
         *            User name needed for NTLM authentication.
         * @param password -
         *            Password needed for NTLM authentication.
         * @param domain -
         *            Domain for the user needed for NTLM authentication.
        public NTLMAuthenticator( URL wsdlurl, String username, String password, String domain ) {
            this.wsdlurl = wsdlurl;
   = wsdlurl.getHost();
            this.username = username;
            this.password = password;
            this.domain = domain;
            this.authenticator = null;     
         * Instruct our NTLM authenticator to use setPreemptiveAuthentication or not. Default is true;
         * @return - true or false
        protected boolean usePreemptiveAuthentication(){
            return true;
         * The {@link Authenticator} is used to setup NTLM authentication to a webservice stub/client. <br>
         * Example:<br>
         * If you extended a Stub object, you would call getClient() or your Stub object.<br>
         * Then super._getServiceClient().getOptions().setProperty(HTTPConstants.AUTHENTICATE, getAuthenticator());<br>
         * <li>This should work with any URL/Soap call but it has only been tested with axis2 stubs.
         * <li> This also used PreemptiveAuthentication.
         * @return - {@link Authenticator} object populated.
        public Authenticator getAuthenticator() {
            if (this.authenticator == null) {
                this.authenticator = new Authenticator();
            List<String> auth = new ArrayList<String>();
            return authenticator;
        public void setAuthenticator( Authenticator authenticator ) {
            this.authenticator = authenticator;
        public String getUsername() {
            return username;
        public void setUsername( String username ) {
            this.username = username;
        public String getPassword() {
            return password;
        public void setPassword( String password ) {
            this.password = password;
        public String getDomain() {
            return domain;
        public void setDomain( String domain ) {
            this.domain = domain;
        public String getHost() {
            return host;
        public void setHost( String host ) {
   = host;
        public URL getWsdlurl() {
            return wsdlurl;
        public void setWsdlurl( URL wsdlurl ) {
            this.wsdlurl = wsdlurl;
    * NTML Support for webservices where our webservice is protected via NTLM.
    * @author Brian Hayes
    public class NTLMReportExecutionServiceStub extends ReportExecutionServiceStub {
        private NTLMAuthenticator endpointAuthenticator;
         * Enables NTML authentication to our SSRS reports by setting the property via setAuthenticeProperty();
         * @param authenticator
         * @throws AxisFault
        public NTLMReportExecutionServiceStub( NTLMAuthenticator endpointauthenticator ) throws AxisFault {
            this.endpointAuthenticator = endpointauthenticator;
        private void setAuthenticeProperty(){
            super._getServiceClient().getOptions().setProperty(HTTPConstants.AUTHENTICATE, this.getEndpointAuthenticator().getAuthenticator());
        public NTLMAuthenticator getEndpointAuthenticator() {
            return endpointAuthenticator;
        public void setEndpointAuthenticator( NTLMAuthenticator endpointAuthenticator ) {
            this.endpointAuthenticator = endpointAuthenticator;
         * Overrides the default URL location.
         * @param wsdlurl
         * @throws AxisFault
        private NTLMReportExecutionServiceStub( String wsdlurl ) throws AxisFault {

Maybe you are looking for